If there was and #emacs distribution without any lisp packages bundled, I'd probably use that.
I had some display freeze issues in #emacs. To my surprise, using the 'Lucid' toolkit instead of 'GTK' solved the problem. (2 weeks of testing showed no problems)
I decided to switch to make the swithc to Lucid permanent as I have a couple of the problems listed there.
It's mainly an invisible change for me. Basically the only time I see a difference is when emacs throws a yes/no dialog at me.
Looking for a way in #emacs to have quoted text in emails collapsed in message-mode.
I envision something like have it all collapsed and replaced by something like '[...]' which could then be used as a toggle.
Anyone have any pointers before I dive into regex hell to write my own.
The best I could find is https://www.emacswiki.org/emacs/HideShow which seem to provide a generic solution which could be adapted.
trying the native-comp branch of #emacs
Goal was simplification.
- systemd config mistakes can lead to silent failures
- I will never master shell script quoting
- moving window (frame) management to a window manager completely is not trivial
- emacsclient has hardcoded action for -a flag, which makes using sockets harder
Full config published here:
I really want to like magit forge in #emacs; it's so nicely integrated, but it is way to slow to be practical for me.
Upgrading to #emacs 27 Mostly for the json stuff.
Migrated to mu(4e) from notmuch for my email; took me "only" 3 days.
- rationale of 'state in maildir only' helps me keep sane when using many machines
- refiling messages is natively supported
- format=flowed support
- UI of mu4e, especially compose and attachment handling
- less glue needed to have a complete workflow
Things I lost:
- remote use over ssh (although the 'mu server' paradigm gives me hope)
It's all a lot simpler now.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!