trash-cli VS zsh-abbr

There's a Freedesktop specification for trashing files that you may consider adhering to: https://specifications.freedesktop.org/trash-spec/trashspec-...

I get that writing a small utility is fun, but if it is just that (for fun), I suggest you put that into the readme. Otherwise, why should I choose your tool over something like https://github.com/andreafrancia/trash-cli, which seems to already be distributed for the major distros? Does your implementation scratch an itch that the myriad of other implementations don't? I'm just curious.

Hard deleting was more necessary on the past when storage was so tiny and expensive, but now we not constantly fighting for space anymore. So treat a rm (and the Unix tradition as a whole) as a product of its time, move undesirable files to the trash instead, you can use this trash-cli for linux.

Not related to Docker, but use the trash-cli trash command to have the recycle bin in the terminal as well.

i ended up using shell-safe-rm plus trash-cli and my own wrapper script around rm that verifies some rules like for example the argument don't start with '/' , if i want to delete for example /home/shin/.local/somefile then the script will not let me and suggest to cd to /home/me/.local and delete from there , same if i do rm /var/somedir.

They're probably talking about something like this rather than a GUI file manager

It's a bad idea to alias rm. You will get trouble on a machine that has no alias. Use trash-cli instead. It's much safer than rm. BTW, don't alias trash as rm because they are different.

For Linux there's [trash-cli](https://github.com/andreafrancia/trash-cli/). Doesn't seem to work for MacOS per this issue (https://github.com/andreafrancia/trash-cli/issues/284), but it suggests to use https://hasseg.org/trash/

Use trash-cli for all your rm -rf needs!

There are a number of foss tools that work with the freedesktop trashcan concept on Linuxes/BSDs, like https://github.com/andreafrancia/trash-cli. Bunch of desktop envs' programs also use this, so it's nearer to OS-wide standardized behavior.

If you have trouble, open a GitHub issue https://github.com/olets/zsh-abbr/issues/new/choose

The abbreviations from Fish will expand the moment you hit space or execute the command. It's basically like an alias, but will expand. However this is not possible in Bash. Zsh itself does not support this, but there is an addon I am using for: https://github.com/olets/zsh-abbr

But you aren't limited to something OMZ specific. zsh-abbr is a manager for "abbreviations" (similar to auto-expanding aliases but with additional tools, and saving everything to a file which can be backed up). And there are zsh snippet managers… I haven't used any so can't speak to them; pet might be the most popular.

Something broke? Open an issue

Enhanced completion: Extend completion by syntax-aware completion, completion with quotes and parameter expansions in prefix texts, ambiguous candidate generation, etc. Also, menu-complete supports selection of candidates in menu (candidate list) by cursor keys, TAB and S-TAB. The feature auto-complete supports the automatic suggestion of completed texts as in fish and zsh-autosuggestions (with Bash 4.0+). The feature menu-filter integrates automatic filtering of candidates into menu completion (with Bash 4.0+). There are other functionalities such as dabbrev and sabbrev like zsh abbreviations or zsh-abbr.

I know. I have an addon for ZSH which mimics the Fish like abbreviations: https://github.com/olets/zsh-abbr

I am on ZSH and prefer abbreviations (with an addon to mimic Fish abbr), because the command will expand on typing and I change it before execution. Also it is then correctly logged as expanded version in the history. However, I also have a few aliases too: