7 ms·
There are tons of goodies in there, and the author is doing a hell of a service to Emacs users. That said, a part of my can't but sigh... Now we have new compl
by arthur_debert 15y ago
There are tons of goodies in there, and the author is doing a hell of a service to Emacs users.
That said, a part of my can't but sigh... Now we have new completion & new electric pairs. How is that going to propagate to other modes? Just the thought of new the work involved in diagnosing which mode is using what, and how to adapt for it gives me the chills.
The package manager looks nice, but how can it handle stuff hosted on a git rep? How are changes show? Without all of this sorted out, it's usefulness is severely diminished.
- nyellin 15y agoSee the discussion about el-get here: https://news.ycombinator.com/item?id=3320458 https://news.ycombinator.com/item?id=3320458 Runs
- mickeyp 15y agoThe completion mechanism is actually the same as what it has always been. `completion-at-point' is Emacs's generic completion framework, and what they've done is replace all those mode-specific hatchet jobs with the more generic one. As for the electric stuff, that's the same story: every mode had its own way of doing it. I used (and still do, not migrated yet!) skeletons for my electric pairing as it did a really good job of handling all the edge cases (you're in a word, you're at a bracket already, etc.)