deadgrep
nushell
deadgrep | nushell | |
---|---|---|
11 | 213 | |
699 | 29,963 | |
- | 1.3% | |
4.4 | 9.9 | |
24 days ago | 6 days ago | |
Emacs Lisp | Rust | |
- | MIT License |
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 -
https://github.com/Wilfred/deadgrep
-
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.
nushell
-
PowerShell: The object-oriented shell you didn't know you needed
I rather nushell for this purpose, it's more fun to write and easier to read.
https://www.nushell.sh/
-
NuShell - Ceci n'est pas une |
These are just three small examples of what this shell written in Rust allows. The features are many and many more, but I'll leave it up to you to discover and enjoy them; I'm currently playing around with it and it's giving me a lot of satisfaction and immediacy, now it has a fixed place among the tools I use when working! The project is Open Source, so if you want to contribute, I invite you, as always, to do so, I leave you the link to the repo here!
- Xonsh: Python-powered, cross-platform, Unix-gazing shell
-
Fish shell 3.7.0: last release branch before the full Rust rewrite
Any thoughts on fish as compared to nushell [0]? It's similar to PowerShell in its philosophy and is also written in Rust.
[0] https://github.com/nushell/nushell
-
jc: Converts the output of popular command-line tools to JSON
> In PowerShell, structured output is the default and it seems to work very well.
PowerShell goes a step beyond JSON, by supporting actual mutable objects. So instead of just passing through structured data, you effectively pass around opaque objects that allow you to go back to earlier pipeline stages, and invoke methods, if I understand correctly: https://learn.microsoft.com/en-us/powershell/module/microsof....
I'm rather fond of wrappers like jc and libxo, and experimental shells like https://www.nushell.sh/. These still focus on passing data, not objects with executable methods. On some level, I find this comfortable: Structured data still feels pretty Unix-like, if that makes sense? If I want actual objects, then it's probably time to fire up Python or Ruby.
Knowing when to switch from a shell script to a full-fledged programming language is important, even if your shell is basically awesome and has good programming features.
-
Ripgrep is faster than {grep, ag, Git grep, ucg, pt, sift}
Maybe if the "popular" shells, but http://www.nushell.sh/ is looking better and better
- "<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
-
jq 1.7 Released
Yeah agreed, especially now that PowerShell is available cross-platform.
Nushell[1] also seems like a promising alternative, but I haven’t had a chance to play with it yet.
[1]: https://www.nushell.sh/
-
The Case for Nushell
I also discovered an existing discussion[1] related to this topic which includes a link[2] to a "helper to call nushell nuon/json/yaml commands from bash/fish/zsh" and a comment[3] that the current nushell dev focus is "on getting the experience inside nushell right and [we] probably won't be able to dedicate design time to get the interface of native Nu commands with an outside POSIX shell right and stable.".
[0] https://gitlab.com/RancidBacon/notes_public/-/blob/main/note...
[1] "Expose some commands to external world #6554": https://github.com/nushell/nushell/issues/6554
[2] https://github.com/cruel-intentions/devshell-files/blob/mast...
[3] https://github.com/nushell/nushell/issues/6554#issuecomment-...
I appreciate what projects like Nushell and Murex are trying to address, but having a saner scripting language and passing structured data in pipelines is not worth the drawbacks for me.
For one, Bash scripting is not so bad if you set some sane defaults and use ShellCheck. Sure, it has its quirks, but all languages do. Even so, the same golden rule applies: use a "real" programming language if your problem exceeds a certain level of complexity. This is relative and will depend on your discomfort threshold, but using the right tool for the job is always a good practice. No matter how good the shell language is, I would hesitate to write and maintain a complex project in it.
And for general QoL improvements with interactive use, Zsh is a fine shell, while still being POSIX compatible.
[1]: https://github.com/nushell/nushell/blob/main/crates/nu-comma...
[2]: https://github.com/nushell/nushell/issues/5027
[3]: https://github.com/nushell/nushell/issues/9310
What are some alternatives?
rg.el - Emacs search tool based on ripgrep
fish-shell - The user-friendly command line shell.
consult - :mag: consult.el - Consulting completing-read
elvish - Powerful scripting language & Versatile interactive shell
emacs-find-file-rg - Find file in current project using rg --files command
starship - ☄🌌️ The minimal, blazing-fast, and infinitely customizable prompt for any shell!
dumb-jump - an Emacs "jump to definition" package for 50+ languages
PowerShell - PowerShell for every system!
Emacs-wgrep - Writable grep buffer and apply the changes to files
alacritty - A cross-platform, OpenGL terminal emulator.
json-diff - Structural diff for JSON files
xonsh - :shell: Python-powered, cross-platform, Unix-gazing shell.