deadgrep
multiple-cursors.el
Our great sponsors
deadgrep | multiple-cursors.el | |
---|---|---|
11 | 17 | |
698 | 2,210 | |
- | - | |
4.4 | 4.4 | |
10 days ago | about 2 months ago | |
Emacs Lisp | Emacs Lisp | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
deadgrep
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Deadgrep (uses ripgrep and evil-collection has a binding) takes me to my happy place -
-
James Dyer: More flexible grepping with deadgrep
theres a package for this that’s god tier: deadgrep
-
advanced-search
this is cool too Wilfred/deadgrep: fast, friendly searching with ripgrep and Emacs
- What have you recently *removed* from your Emacs configuration?
-
Navigating an enormous code base
rg.el or deadgrep: Emacs interfaces to ripgrep, a grep-like tool that is very fast. This lets us search across a large number of files for a pattern of text. The disadvantage of searching for text is that if you are looking for the method called foo and there are hundreds of them that exist, it can be hard to know which one you really want. On the other hand, at the scale and complexity that you are talking about, I can imagine that more IDE-like tools just start failing.
-
If you have never used wgrep with rg.el to rename a function in several files, try it | that will blow your mind
Yes in this area (text search) there is many alternatives. Wilfred Hughes (author of deadgrep) has listed them in: https://github.com/Wilfred/deadgrep/blob/master/docs/ALTERNATIVES.md
-
ripgrep is fantastic | Emacs is fantastic | BOOM you get the fantastic rg.el
Anyone interested in this should also check out deadgrep: https://github.com/Wilfred/deadgrep
- Difftastic: A diff that understands syntax
-
Is there a magit-like interface for grep?
Deadgrep does this, IIUC (I use ripgrep.el instead, but I think deadgrep does something like what you want)
-
Alternatives to two swiper/counsel commands
deadgrep is an interface to ripgrep.
multiple-cursors.el
-
IRS will officially launch free online tax filing service for 2024 tax season
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.
-
packages/features/settings that slow Emacs down
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.
-
Multiple-cursors error on Emacs 29.0.60
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:
-
Best way to "process" a large-ish text file?
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.
-
Multi-cursor code editing: An animated introduction
You'll need to install an extension for it, but yes it does. Here is one example: https://github.com/magnars/multiple-cursors.el
- Let's share your top 3 packages that you can't live without.
-
How to do this Vim Trick in Emacs?
You can do something similar with multiple cursors.
-
If you have never used wgrep with rg.el to rename a function in several files, try it | that will blow your mind
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:
-
[Question] multiple cursor and end of line
There is also multiple-cursors.el, which looks the closest to what you want, but it's also the buggiest.
-
buggy behavior in `mc/mark-all-*-like-this` variants of multiple-cursors
multiple-cursors issue tracker is closed and before continuing to troubleshoot the issues the mark-all-*-like-this variants are giving me when i use them from this hydra wanted to check if anybody else has seen these or has any hints (i tried adding one of the offending commands, e.g. `mc/mark-all-symbols-like-this-in-defun` to both of the variables in `mc-lists.el` to no avail) - the issue is that it tends to give me an extra cursor, and sometimes bug out with error message:
What are some alternatives?
rg.el - Emacs search tool based on ripgrep
doom-emacs - An Emacs framework for the stubborn martian hacker [Moved to: https://github.com/doomemacs/doomemacs]
consult - :mag: consult.el - Consulting completing-read
helix - A post-modern modal text editor.
emacs-find-file-rg - Find file in current project using rg --files command
LunarVim - 🌙 LunarVim is an IDE layer for Neovim. Completely free and community driven.
dumb-jump - an Emacs "jump to definition" package for 50+ languages
kakoune - mawww's experiment for a better code editor
Emacs-wgrep - Writable grep buffer and apply the changes to files
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
json-diff - Structural diff for JSON files
hydra - make Emacs bindings that stick around