trash-cli VS fast-syntax-highlighting

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.

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

You can use trash-cli instead. I rarely use rm now.

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.

POSIX compatibility/compliance. That being said, there are various trash programs available, namely trash.

I recommend installing trash-cli for a file-system independent way of recovering deleted files, and then (most importantly) training your muscle-memory to type trash instead of rm. (And also don't alias rm to trash either, as one day you'll be on a device where trash-cli is not installed and wham).

I’m concerned because I found this repo https://github.com/zdharma/fast-syntax-highlighting which tries to imitate the old repo (before it was deleted). It’s a fork from the z-shell one. I don’t know if they’re both from the sane owner but I find it sketchy. Also z-shell doesn’t have as many stars as zdharma-continuum.

Even http://zdharma.org/ is gone

I use https://github.com/zdharma/fast-syntax-highlighting which highlights git --version differently than git --asdf. AFAIK it uses the completions to "know" what options are valid.

Syntax highlighting at https://github.com/zdharma/fast-syntax-highlighting

# Plugin: zsh-abbr # Fish like expansion of abbreviations. # https://github.com/olets/zsh-abbr . /home/tuncay/.config/zsh/zsh-abbr/zsh-abbr.zsh # Plugin: zsh-autocomplete # Realtime auto completion. # Note: Remove any calls to `compinit` from `.zshrc`. # https://github.com/marlonrichert/zsh-autocomplete . /home/tuncay/.config/zsh/zsh-autocomplete/zsh-autocomplete.plugin.zsh # Plugin: fast-syntax-highlighting # Syntax highlighting like source codes in an editor. # https://github.com/zdharma/fast-syntax-highlighting . /home/tuncay/.config/zsh/fast-syntax-highlighting/fast-syntax-highlighting.plugin.zsh

I'm not sure what you mean. If you mean syntax highlight of your commands inside the neovim terminal then you have to zsh and have either zsh-syntax-highlighting) or fast-syntax-highlighting setup and then set your shell inside neovim to zsh.