-
Notifications
You must be signed in to change notification settings - Fork 459
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 --no-cwd-file
to close
#1629
Comments
Nice to have! Anyone want to give this a go? |
Willing to have a crack at it, I've not been using Yazi all that long, but I presume this relates to the difference between exiting to the current directory Yazi is in (That the user has navigated to) vs. returning to where the shell spawned the process. |
I'm also trying to understand the issue. As to the problem you mentioned, it can be resolved by adding this to |
I have part content for a PR, though I need to do further testing and still somewhat unsure of what exactly OP is after. |
If I understood correctly, OP means to add the
and at that point, we need to pass the yazi/yazi-core/src/manager/commands/quit.rs Lines 11 to 13 in 631afd0
Let me know if this is what you want! @kockahonza |
Hi everyone! Sorry for my absence I was offline on a trip for a while. But yes I was thinking of exactly what is described by @sxyazi . Essentially so that if the |
Tracked by #51 |
I'm going to lock this issue because it has been closed for 30 days. ⏳ |
yazi --debug
outputPlease describe the problem you're trying to solve
As the title says I think it might be worth adding the
--no-cwd-file
option to theclose
command as well asquit
for whenclose
exits yazi (when it closed the last tab). It's a very small thing but seems reasonable and I could personally use it as I preferclose
overquit
.I might be able to implement this myself but not right now as I'm too busy, maybe in a couple of months.
Would you be willing to contribute this feature?
Describe the solution you'd like
Pretty clear from the above I think.
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: