multiple-cursors.el VS org-roam

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.

I keep absolutely everything in a single folder. Saved documents, images, movies, financial records, game saves, it doesn't matter. My hierarchical naming scheme takes care of organization. On the odd occasion I actually need a folder, I just append ".d" to the filename.

I use . as a hierarchy delimiter, so file extensions are just part of the hierarchy, and I can have multiple files with the same name except for the extension. For example, "film.spongebob.png" is a photo of spongebob, "film.spongebob.org" is a note about spongebob, and "film.spongebob.s1.e7" is my favorite episode.

I use org-roam [1] for note-taking and task/time-management. I absolutely require a plain-text system so it either had to be markdown or org-mode. Emacs was the deciding factor, else I would have still been using Dendron [2]

If OneNote is your thing, I'd probably recommend Obsidian [3] over org-roam. Despite it being the greatest program ever created, Emacs is a lot to learn "just" for taking notes.

If you like VS Code, check out Dendron. It's the one that got me into more serious PKMS instead of just chucking notes in a folder all willy nilly.

- [1]: https://www.orgroam.com/

- [2]: https://www.dendron.so/

- [3]: https://obsidian.md/

I'm using org-roam to keep my notes, which generally works well for me. There's one thing I am missing and I'm wondering if I just overlooked it, or whether it simply doesn't exist.

Org-Roam is a Roam-inspired Emacs mode that builds on top of org mode. Every node (aka note) has a unique ID that's different from its name. Every link from node A to node B actually links to the ID, so you can change node B's name without affecting the link. When you're on node B, you can open the Roam buffer and it will show you all of the links that point to that node.

Org Mode. I can export my notes to LaTeX or HTML and keep things tidy in a zettelkasten with org-roam.

Of course, the real power-user move would be to use Emacs with Org-Roam, but you have to be prepared to dive deep into the rabbit-hole. If you don't, it won't be worth it. If you do, you'll be handsomely rewarded. I know because I have, and I can highly recommend it if you like tinkering with and customising your tools. IMO, Doom Emacs is the way to go nowadays.

I'd highly recommend Org-roam. It's what has enabled me to actually start consistently keeping notes (and being able to retrieve/access them later). It's very easy with Org-roam to quickly add new notes, or add information to old notes, and the links/backlinks make (re)discoverability very easy.