-
Notifications
You must be signed in to change notification settings - Fork 259
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
Open terminator [2.0.1] in same working directory #262
Comments
This is how it works for me. If I open terminator from another terminal emulator, it opens in the directory I launched it from? What OS are you using? |
Oh, ok! I'm on Arch Linux. |
Same issue here, |
I've poked the Arch packager to see if he can reproduce. Can you check to see if vte-common is installed? I don't see a dependency for it, but it does help with this. |
The relevant code is here https://github.com/gnome-terminator/terminator/blob/master/terminatorlib/cwd.py if you don't have the OSC-7 escape sequence installed, and is called from https://github.com/gnome-terminator/terminator/blob/master/terminatorlib/terminal.py#L236 if you want to investigate further. |
Yes, vte-common is installed. |
If you modify the file manager to run |
Can you run |
|
This used to be the behaviour, but seems Terminator 2.0.1 changed to default to using `$HOME` instead, breaking this. See gnome-terminator/terminator#262.
In 1.92, terminator opens in the same working directory as the "parent", whereas in 2.0.1, it always opens in $HOME.
I believe the functionality should be how it was in 1.92, the same way it is in gnome-terminal (and others?).
How to reproduce:
Simple use case:
When launching a terminal from the file manager, you want it to be started at the current folder.
The text was updated successfully, but these errors were encountered: