-
-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for custom trash command #1978
Conversation
Haven't updated the docs yet. Some of the patches might need updating too. I'll fix them if this approach is deemed acceptable. Looks like a relatively easy way to support arbitrary trashing utilities, and we're getting lots of request for custom trash utility support. What do you guys think? @jarun @KlzXS |
Approach looks good to me. |
066eb3a
to
3a91429
Compare
this makes it so that if $NNN_TRASH is set to a string other than "1" or "2" then it is accepted as the trash command to run. this allows us to support arbritary trashing utilities while also maintaining backwards compatibility for older "1" & "2" values. Fixes: jarun#1168 Fixes: jarun#1963 Fixes: jarun#1960 Fixes: jarun#1761
CI is failing. Please check:
|
Thank you! Please update the docs so that users can easily use it. |
I've already updated the manpage in this PR. Will update the wiki soon. |
I meant the wiki... |
Done. |
Thank you so much! |
this makes it so that if NNN_TRASH is set to a string other than "1" or "2" then it is accepted as the trash command to run.
this allows us to support arbritary trashing utilities while also maintaining backwards compatibility for older "1" & "2" values.
Fixes: #1168
Fixes: #1963
Fixes: #1960
Fixes: #1761