Yes, exactly this. The camel breaking straw for me was yet another iteration of 'come on, let's tame this beast, find package X to scratch itch Y, update and watch something break. Spend hours numptying and googling around, give up, fresh re-install, do some paid work'. Rinse and repeat.
Cursive - from day one it has worked for what I need out of the box. Do I miss some things from emacs? Sure - keyboard navigation, buffer switching, kill ring, ability to run over ssh on the powerful company servers, undo-tree and so on. Do I hope that one day when I grow up I will be good enough to build me own emacs-based-editor - sure :). I had better stop thinking about emacs as it is feeding my ever-present 'grass is greener' gene.... On 31 March 2015 at 10:54, Phillip Lord <phillip.l...@newcastle.ac.uk> wrote: > Alexis <flexibe...@gmail.com> writes: > >> Colin Yates <colin.ya...@gmail.com> writes: >> >>> I used it a few years back >> >> [snip] >> >>> [and] even after man-months spent tinkering, hunting down the right version >>> on MELPA or MARMALADE (or whatever it is called) >> >> i basically only use MELPA and GNU ELPA. In terms of the ~200 packages i've >> installed from MELPA, i can't remember having to deal with versioning issues >> at all. Further, despite some people fretting about the theoretical lack of >> stability of packages on MELPA, i've only rarely had to deal with broken >> packages - and those breakages have been fixed very rapidly by the >> maintainers. > > I have. Mostly with Clojure as it happens -- the move from slime to > nrepl was quite painful. And the lack of stability on MELPA was a > significant cause. > >> *nod* >> >> However, Emacs configuration management has, i feel, improved significantly >> over the last couple of years, with things like `use-package`: >> >> https://github.com/jwiegley/use-package >> >> enabling one to create easily-reproducible config setups across >> environments/machines. > > This was the cause of all my grief with MELPA though. My setup is > use-package based (actually, I added the ELPA/package.el integration). > I sync my .emacs across machines, and use-package auto-installs missing > packages. This meant I got different versions on every machine, > depending on when the auto-install happened. > > Fingers crossed more package authors add support for MELPA stable. I use > it exclusively now. > > Phil > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
