sd
micro-editor
sd | micro-editor | |
---|---|---|
31 | 227 | |
5,369 | 23,947 | |
- | - | |
8.0 | 9.4 | |
2 months ago | 2 days ago | |
Rust | Go | |
MIT License | 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.
sd
-
Essential Command Line Tools for Developers
View on GitHub
-
Ripgrep 14 Released
I wanted to like sd but it doesn't support my main use case of recursive search/replace. Imagine every time you wanted to grep some files you had to build a find+xargs+rg pipeline... it just takes me out of the flow too much. I'm glad people are posting other options here, I'm looking forward to trying them.
https://github.com/chmln/sd/issues/62
-
🐚🦀Comandos shell reescritos em Rust
sd
-
sed cheatsheet
https://github.com/chmln/sd ftw (sed rebuilt in rust, much easier imho) ;-)
-
What modern utilities should be a standard part of a modern unixy distro?
sd is a more intuitive alternative to sed, focussing on making find and replace easier - which is all I ever used sed for.
https://github.com/chmln/sd
-
Delete all occurrences of a string
If it's in multiple files? To be honest, I'd just use a terminal and sed (or sd if you want something with a more friendly interface).
- Neovim locks up on big files while doing a replacement
-
sd: your script directory
I love the idea and I'll try it out, but a heads up in case the author is around: the name sd clashes with another tool [0], which works as an alternative to sed.
I use that one pretty often, so maybe my first managed script will be one which symlinks binaries :)
[0] https://github.com/chmln/sd
- Intuitive find and replace CLI (sed alternative)
-
Rust Easy! Modern Cross-platform Command Line Tools to Supercharge Your Terminal
sd is a find-and-replace CLI, and you can use it as a replacement for sed and awk. It is way more user-friendly and modern. It is also magnitudes faster than sed.
micro-editor
- Ask HN: What software sparks joy when using?
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
-
Go: What We Got Right, What We Got Wrong
Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:
- gdu: a NCDU clone, much faster on SSD mounts [1]
- duf: a `df` clone with a nicer interface [2]
- massren: a `vidir` clone (simpler to use but with fewer options) [3]
- gotop: a `top` clone [4]
- micro: a nice TUI editor [5]
Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.
[1]: https://github.com/dundee/gdu
[2]: https://github.com/muesli/duf
[3]: https://github.com/laurent22/massren
[4]: https://github.com/xxxserxxx/gotop
[5]: https://github.com/zyedidia/micro
-
Text Editor: Data Structures
> The worst way to store and manipulate text is to use an array.
Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.
Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.
Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).
[1] https://github.com/zyedidia/micro
[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...
[3] https://github.com/cessen/ropey/pull/67
- A nano like text editor built with pure C
-
A simple guide for configuring sudo and doas
There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:
-
what terminal emulator do you use and why?
found that micro has dedicated info page for copy paste
-
Microsoft is exploring adding a command line text editor into Windows, and it wants your feedback
micro: winget install zyedidia.micro
- What is the best basic ass text editor?
What are some alternatives?
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
helix - A post-modern modal text editor.
neomutt - ✉️ Teaching an Old Dog New Tricks -- IRC: #neomutt on irc.libera.chat
filemanager-plugin - A file manager plugin for the editor "Micro"
useful-sed - Useful sed scripts & patterns.
kakoune - mawww's experiment for a better code editor
hck - A sharp cut(1) clone.
xclip - Command line interface to the X11 clipboard
pomsky - A new, portable, regular expression language
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
joshuto - ranger-like terminal file manager written in Rust
editorconfig-core-go - EditorConfig Core written in Go