sad VS sd

also check out sad a more intuitively named sd that allows for fancy pipe input

If i were to write this in a faster language, it would be in Rust, since I already have a relativly successful CLI text edit tool written in it, and it's fast as fuck too.

Here is link number 1 - Previous text "sad"

https://github.com/ms-jpq/sad - when you need PCRE in sed

what you really want is sad, https://github.com/ms-jpq/sad

sad CLI search and replace | Space Age seD tcount Count your code by tokens, types of syntax tree nodes, and patterns in the syntax tree. A tokei/scc/cloc alternative. nushell A new type of shell fclones Efficient Duplicate File Finder hunter The fastest file manager in the galaxy! teip Select partial standard input and replace with the result of another command efficiently cb Command line interface to manage clipboard semiuniq A uniq-like tool for removing nearby repeated lines in a file" dua-cli View disk space usage and delete unwanted data, fast. htmlq Like jq, but for HTML. pipecolor A terminal filter to colorize output crowbook Converts books written in Markdown to HTML, LaTeX/PDF and EPUB delta A viewer for git and diff output mdcat cat for markdown pueue Manage your shell commands. gitui Blazing 💥 fast terminal-ui for git written in rust 🦀 pipr A tool to interactively write shell pipelines. rename Rename your files using your favorite text editor bropages Highly readable supplement to man pages from http://bropages.org. Shows simple, concise examples for commands with syntax highlighting. html2md convert simple html documents into markdown bk Terminal Epub reader rs A safe Rust crate for working with the Wayland clipboard. viu Simple terminal image viewer written in Rust. alacritty A cross-platform, OpenGL terminal emulator. wezterm A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust

Check it out at my github

sad

Thanks, if you like it you can also try my batch text editor.

Prefixing these utility scripts is a nice tip, I used to do that as well.

Some time ago I found https://github.com/ianthehenry/sd though. It's a light wrapper around your own scripts which provides namespaces, autocompletion, custom help texts + some other QoL enhancements around that. It improves discoverability and usability a lot, very happy with it.

A few things that can help with memory:

- spaced repetition for stuff that you use sporadically. I use Anki, it's great. For how to use it, this article is great: https://borretti.me/article/effective-spaced-repetition. I've found a positive feedback loop where the more I know how to do things without looking anything up, the more I use the CLI, the easier I remember things, the more things I discover, etc. I read once that when learning a new language, you should aim for content where you know 80%/90% already. It seems to be true for learning the CLI, and especially for integrating that learning into my day to day job.

- sd (https://github.com/ianthehenry/sd) for lowering the cost of creating a "documented alias". Before that I made aliases with either alias, or bash functions, all starting with "," to quickly see all which are "mine" (I read that trick in an article that I can't find), now the more complex stuff is in sd with some documentation.

Yeah :( https://github.com/ianthehenry/sd/issues/9

The trouble is `sd` is just so easy to type on a qwerty keyboard, and it's such a nice mnemonic for "script directory." I've thought about renaming it, but I can't think of anything I like nearly as much.

zsh can do this if you set the PATH_DIRS option, but if I remember right it doesn't autocomplete deeply nested directories, just one level.

I made a little tool that dispatches hierarchical commands in a slightly nicer way, with intelligent autocomplete with command descriptions: https://github.com/ianthehenry/sd