News for hackers. Stuff that matters.
Re:Zed, a collaborative code editor, is now open source by sooheon on Thursday January 25, 2024 @07:05AM (#39128642)
Emacs still blocks input on simple things like package updates though.
Re:Zed, a collaborative code editor, is now open source by benreesman on Thursday January 25, 2024 @07:08AM (#39128654)
Give straight.el (among others) a shot. Combined with use-package you don’t have to worry about that these days.
Re:Zed, a collaborative code editor, is now open source by sooheon on Thursday January 25, 2024 @07:12AM (#39128690)
Ah ok. Last time I used straight it still blocked input on straight-update-all, didn’t realize they changed this.
Re:Zed, a collaborative code editor, is now open source by benreesman on Thursday January 25, 2024 @08:59AM (#39129595)
There's a little tweaking sometimes.

Most examples you'll see of `straight.el`/`use-package` configurations will have some version of: `(use-package something-cool :ensure t :config ...`. The `:ensure t` clause will cause it to fall back on `package-install` in the event it's not bolted into your local Cargo-style-own-the-world-and-dont-break repo mirror. Disks are big, it's like the right default now.

But if you've got a package that's mis-specified in terms of where on `github` or wherever that `striaght` is supposed to find it, you can find it tapping `elpa.org` on the shoulder at a time when the UI thread is also doing blocking network IO.

The `Messages` and/or `straight` buffers will have warnings about this, so it's fixable to find the offending package and it'll stay fixed, but in fairness what you're describing is possible.

Re:Zed, a collaborative code editor, is now open source by bergheim on Thursday January 25, 2024 @09:44AM (#39130062)
Elpaca [1] does not do this. I use it and it works a treat.

1: https://github.com/progfolio/elpaca