multiple-cursors.el VS use-package

You'll need to install an extension for it, but yes it does. Here is one example: https://github.com/magnars/multiple-cursors.el

For me, the beauty of Beancount[0] is that it's just text files in Git. There's a web UI I use for generating reports, and a Python API with which I hacked together some import/export scripts, but 99% of my interactions with it are via Emacs[1] and Magit.

A ton of repetitive bookkeeping tasks become so much easier when you can copy and paste, or use keyboard macros or something like multiple-cursors[2], rather than have to click tens or hundreds of times in a GUI. Many years ago I used QuickBooks, and basic tasks like importing a bank statement took at least an order of magnitude longer than they do now.

Having my company's books in Git is also huge when it comes to auditing, concurrency, backups, and figuring out where things went wrong when accounts don't balance. As mentioned in another comment: `git diff` is a really powerful tool and it's awesome to be able to check out the books as they existed at a particular point in time. `git blame` is great for when things don't balance. Writing meaningful commit messages and comments keeps me sane when I try to remember a year later why something is recorded the way it is.

The biggest downside—or advantage, depending on how you look at it—is that there's no default or built-in chart of accounts, so you need a certain level of accounting acumen (or professional advice) to set things up at first. I'm pretty sure GnuCash aims to be more plug-and-play, whereas Beancount is more akin to a programming library that you use to build an accounting system that works for you. I agree with the grandparent commenter, who said that text-based accounting is "the best and most flexible accounting experience I've ever had." But the cost of that flexibility is that a certain level of base knowledge is a prerequisite.

[0]: https://beancount.io/

[1]: https://github.com/beancount/beancount-mode

[2]: https://github.com/magnars/multiple-cursors.el

The original multiple cursors package is amazing for what it is, but it scales very badly. Emacs is efficient when editing at one place at a time (as you'd do normally), and when mc replicates all the edits character-by-character for all the cursors, it does the very opposite of this: many edits all in very different places. It works quite well when using just a few cursors, but going above a dozen of them causes them to be visibly sluggish.

Recently multiple-cursors has been unusable for me on Emacs 29.0.60 (not a release yet). Movements (and possibly other operations) don't work with the following error:

If you intend to use Emacs for this (as opposed to some external script), you're probably better off using the keyboard macros or a regular search&replace instead of multiple cursors (I assume the Magnars flavor of them). As flexible as they are, they don't scale well and they get exponentially slower the more cursors you have. Having 2500 cursors sounds insane.

You can do something similar with multiple cursors.

Then, in *rg* buffer, we transform org-link-expand-abbrev into org-link-RENAMED the way we prefer (we have all the Emacs power, some of us might use query-replace, other might use multiple-cursors.el, other iedit, etc.). And so *rg* buffer looks like this:

There is also multiple-cursors.el, which looks the closest to what you want, but it's also the buggiest.

Another way would be to redefine parts of the bind-key macro or its use-package support functions

The package-install call installs use-package that provides a utility of the same name to make it easier to manage packages. It's admittedly a little overkill for this specific config, but it's a cheap investment that sets you up for later success.

Granted, the Doom macro makes your code looks nice and compact. But you can get very close to that just by using do-list and define-key together. Or by using the bind-key.el package, which is included with Use-package.

> Deps is well documented.

> The issue I personally found is that I needed to look at a bunch of OS project's deps.edn to see how people commonly structure things. Other than that it is a simple tool.

This strikes me as a contradiction, because if it was well documented you wouldn’t need to look at other people’s configs to see how to use it.

My experience with deps.edn is that every time I start a project and make a deps.edn file, I immediately draw a blank and don’t know how to structure it, so I open ones from other projects to start lifting stuff out of them.

I still don’t know how to reliably configure a project to use nrepl or socket repl without just using an editor plugin. I definitely have no idea how to use those in conjunction with a tool like reveal.

To me, none of that is simple. Simple would be like Emacs’ use-package. With that I know how to add dependencies, specify keybinds, and do initialization and configuration off the top of my head. And it has really nice documentation with tons of examples.

https://github.com/jwiegley/use-package

Since you are doing code development, the first things to go for would be setting up your emacs packaging (installing use-package and melpa (use-package's documentation covers this) so you have more packages to choose from (do be careful to not just pick things willy nilly but research them a bit first)) and then setting up lsp-mode. lsp-mode lets you use LSP servers for the specific programming languages you work with in a somewhat unified fashion. You then need to install and setup the LSP servers for the languages you use, and possibly install language specific Emacs packages as support (note, Emacs has builtin functionality for many).

I'm using use-package as my package manager and the package ligature for the ligatures.

I have been crafting my emacs config for about 10 years. I started with vanilla and intentionally stayed away from frameworks. About two years ago I declared config bankruptcy and went down for a rewrite using use-package and straight.

ref: https://github.com/radian-software/straight.el https://github.com/jwiegley/use-package

use-package! is a macro over use-package, and respect its syntax, with a few additions. Useful reference on use-package keywords.