-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
--cwd=current doesn't work properly with nnn #3024
Comments
I dont use nnn so I have no idea what ! does. But cwd works by using the |
Thanks. |
@kovidgoyal can you check if OSC-7 can be supported? |
I'm afraid I'm not a fan of osc 7, sorry. Just imagine if a shell sets it and then runs a program like vim that does not set it but that program cds to another directory. Then the terminal that implements OSC 7 will open the wrong directory. Basically once one program uses it, all programs have to use it, and that is never going to happen. Then there are the issues with remote hosts, where you have to use hostname to detect and ignore OSC 7 from remote hosts, which is fragile. When you relinquish the tty to another process such as a spawned shell you should mark that process as the foreground process for the tty. And mark yourself as the foreground when you resume control. This is how shells do it. See for example: https://unix.stackexchange.com/questions/403530/who-changes-the-foreground-process-group-of-a-terminal?noredirect=1&lq=1 It is important to note that after making another process group the foreground you must not write to the tty or change its attributes until that process is dead, otherwise you will get a SIGTTOU which will cause a hang: https://www.gnu.org/software/libc/manual/html_node/Job-Control-Signals.html |
Describe the bug
When I navigate to a directory in
nnn
, exit it with!
and open another window withlaunch --cwd=current
, it opens inside home directory. Actually, after doing such an action, even if icd
outside, it keeps opening inside the home directory.Environment details
Void Linux, musl version
Additional context
My kitty configuration
The text was updated successfully, but these errors were encountered: