You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pressing F4 in PCManFM-Qt should open terminator with currently opened directory as working directory
Current Behavior
If no terminator is running, the behaviour is as-expected.
If another instance is already running which was not started by pressing F4, terminator will open with home directory, not the one opened in PCManFM-Qt
If another instance is already running which was started by pressing F4, terminator will open with working dir from another terminator window, not the one opened in PCManFM-Qt
Possible Solution
Tried setting /usr/bin/terminator --working-directory %s, but that didn't work. Peeking the process tree showed that every new terminator window is actually a child of the first terminator process spawned.
Steps to Reproduce (for bugs)
Install terminator terminal emulator
Set it in PCManFM-Qt preferences (does not matter whether it is selected or its path is entered manually)
Open terminator, note its cwd
Browse to a directory different than the one above, press F4 and cwd.
Context
This is probably a duplicate of #231
Also, I am almost certain this used to work until recently.
System Information
Distribution & Version: Arch Linux, updated Jan 2021
Kernel: 5.10.4-arch2-1
Qt Version: 5.15.2
libqtxdg Version: 3.6.0
Package version: 0.16.0-1
The text was updated successfully, but these errors were encountered:
Expected Behavior
Pressing F4 in PCManFM-Qt should open terminator with currently opened directory as working directory
Current Behavior
Possible Solution
Tried setting
/usr/bin/terminator --working-directory %s
, but that didn't work. Peeking the process tree showed that every new terminator window is actually a child of the first terminator process spawned.Steps to Reproduce (for bugs)
cwd
cwd
.Context
This is probably a duplicate of #231
Also, I am almost certain this used to work until recently.
System Information
The text was updated successfully, but these errors were encountered: