swiper VS GNU Emacs

This is a good improvement. Personally though I left isearch behind. For further search convenience / functionality I highly recommend swiper.

Next you "only" have to remember (elisp) function names. "Completion UIs" like ivy/counsel, icomplete, helm or vertico/consult, give you a nice auto completion list on M-x (choose the one of them, you like the most). Some of those Completion UIs will display existing keybindings and a short documentation for commands, near the auto complete candidates. So you will start to remember more keybindings without "learning sessions", just because invoking functions via keybindings is much faster (more convenient).

Proposal 4 (group-function). This one is an actual addition, which allows candidate gouping in the style of Helm. Note that it is a pure addition. Completion UIs and completion packages work perfectly fine without it. It wouldn't be difficult to add support to Ivy. I wrote the patch.

For the unfamiliar, Swiper is a part of Ivy which lets you search through your buffer with a preview of match candidates: you type some text you're looking for, and up pops a list of matching lines in the minibuffer that you can then use the arrow keys, C-n C-p etc. to scroll through and select the one you want.

When I started using Emacs I was following the setup outlined by System Crafters, which I still think is a really good introduction. But, over the last few months I've started to replace packages with more "minimalist" or "stripped down" packages. I've switched from Ivy and Counsel to Vertico and Consult, and recently I switched from company to corfu for auto-completion.

Ah, neat. I hadn't considered appending comments for searchability. I'm currently getting searchabiity from M-x dwim-... and ivy completion.

Great question. I have one big file with a few hundreds book and quotations from them. Problem is with newlines. When I copy text from kindle it doesn't have newlines because it's depends on font size. So every quotation from book is on one line - could be few thousands chars. I use visual-line-mode and there is a big problem with that. Like swiper would just freeze your emacs if you try to search. https://github.com/abo-abo/swiper/issues/925 Anyone have same problem?

I've been in love with Emacs and Org Mode for over a decade mostly as a user, only writing basic Elisp in my .emacs initialization file. Writing this book made me even more enamored with Emacs as I learned to write a few packages, and spent much time browsing the Org source code, especially around the export engine [1]. It was useful going through one.el source code as well [2]

[1] https://github.com/emacs-mirror/emacs/blob/master/lisp/org/o...

show-paren-mode is a well-known minor mode. Enabling it highlights matching opening and closing parentheses. Here’s an example:

While embracing analog tools, I've also refined my digital organization using ORG mode in Emacs. The system has evolved to become more structured and efficient.

Meanwhile, Richard Stallman at MIT took a different path with Emacs in 1985. Where Vi focused on speed and efficiency, Emacs pursued extensibility and customization. These contrasting philosophies - minimal versus expansive - would shape development tools for decades.

GNU Emacs

Unexpected evaluation is never a feature, Emacs should at least warn and prompt before executing code in a file that somebody opens.

What's of greater importance here is not this specific security issue, but the default behavior of MIME handling in Emacs which can turn any unexpected evaluation bug (which we are likely to see more of) into remote code execution. We've had a previous Org security issue in exactly the same vein [1] and the Emacs MIME defaults are still unsafe. Of course, one can change them (non-trivial and related documentation is extremely confusing, see [2] for a possible solution) but really Emacs should not come with these defaults.

[1] https://github.com/emacs-mirror/emacs/commit/befa9fcaae29a6c...

While Emacs has been around since the 70s. Its extensive library of add-on packages, which allow me to tailor the editor to their specific workflow and needs. Syntax highlighting, code completion, version control integration, and a built-in terminal emulator, making it suitable for me for a variety of programming tasks. ‍