Hi. xfce4-terminal version 0.8.9 broke the action of opening the terminal in a specific directory. Steps to reproduce: * open the root `/` directory in thunar or doublecmd (the latter if it is configured with xfce4-terminal as its terminal) * try to open terminal in that directory Expected at this point: terminal is opened at this directory. This is the behavior of xfce4-terminal-0.8.8 as well. Actually: the terminal is opened at `~`, no matter where you were.
Hi, thanks for the report! Apparently, the working directory doesn't get passed from 'exo-open' into the terminal; I will look into this. For now, you can use the following workaround: in Thunar, go to Edit -> Configure custom actions... and edit the "Open Terminal Here" action - add '--default-working-directory %f' to the end of the command line. This will pass the working directory directly into the terminal. The action on my system looks as follows with the workaround: exo-open --working-directory %f --launch TerminalEmulator --default-working-directory %f
I'm not sure I got it correctly. If I downgrade xfce4-terminal to 0.8.8, everything works as expected. Do you mean that when I explicitly call xfce4-terminal from doublecmd, the process switches to `exo-open` and then back to `xfce4-terminal`? If not, then the bug is in xfce4-terminal itself, right?
Alternative way to test: * open xfce4-terminal * go to to any other directory than your home * execute `xfce4-terminal` from inside the already existing terminal With 0.8.8, same directory would be used. With 0.8.9, you are reset to home.
I'm not saying there isn't a bug in xfce4-terminal, I'm just suggesting a way around the bug.
@Igor, I meant this line: > Apparently, the working directory doesn't get passed from 'exo-open' into the terminal; I will look into this. But anyway, I got it, thanks!
Igor referenced this bugreport in commit 7b024aa09bd4553269d616835dac6fff19d9fcf1 Revert "Respect the "Working Directory" setting when opening initial window" https://git.xfce.org/apps/xfce4-terminal/commit?id=7b024aa09bd4553269d616835dac6fff19d9fcf1
I've reverted the change that broke the functionality and am going to make a bug-fix release to address this bug. Thanks again for submitting it!
Great, thanks!
You're welcome!