News for hackers. Stuff that matters.
Re:Zed, a collaborative code editor, is now open source by lgessler on Wednesday January 24, 2024 @02:37PM (#39121695)
I tried to get into emacs a few years ago and just got fed up with the incredible regularity with which packages broke during routine updates. It was at least an hour a week on average, I feel, conducting bug hunts for either minor (this or that keybind/function doesn't work) or major (I can't get any packages to load) bug hunts. Was I doing something wrong? How do emacs people deal with this?

Admittedly, I was using Spacemacs which probably has way more packages than a bespoke emacs configuration, but you must understand if people get turned off when they ask you how to use an editor and your answer is "first, spend a few weeks setting it up and understand how each of your many packages works".

Re:Zed, a collaborative code editor, is now open source by philsnow on Wednesday January 24, 2024 @04:13PM (#39122722)
> packages broke during routine updates

> How do emacs people deal with this

The same way anybody working with any package system does, by pinning ancient versions and/or just never updating all packages, at least for packages that aren't so widely used that they pretty much are never broken

Re:Zed, a collaborative code editor, is now open source by unhammer on Thursday January 25, 2024 @02:38AM (#39127188)
1. Install from stable.melpa (or gnu elpa) instead of melpa (and pin to that)

2. git add .emacs.d/elpa

3. Don't click update all the time.

Re:Zed, a collaborative code editor, is now open source by Tomis02 on Thursday January 25, 2024 @05:26PM (#39136257)
> How do emacs people deal with this?

Stockholm syndrome.