symlinks resolved when opening new window or tab about roxterm HOT 3 CLOSED

I don't think I can do anything about that. It gets the cwd by reading it from /proc//cwd which points to the resolved location if you got there via a link. But you have made me realise that there are problems in the code for doing this so I should fix it.

Original comment by: realh

from roxterm.

It's interesting that xterm appears to have the correct behaviour when a new window is opened. Maybe you could implement it into ROXTerm however xterm does it?

Original comment by: jonorthwash

from roxterm.

The main difference is that xterm uses a separate instance for each window so each one inherits the cwd from its parent without having to do anything. All ROXTerm windows share a single instance even if you run each one from the command line, unless you use the --separate flag. This means they have to have their working directory set explicitly, otherwise they'd all be stuck with whatever was the cwd when the original instance was run.

When a second instance is run from a command it reads the cwd and sends a dbus request to the original instance to open a new window with that directory and all the other options. It seems that getcwd() and g_get_current_dir() both follow symlinks, but I stumbled across GNU's get_current_dir_name() which appears not to, so I've changed roxterm to use that when it's available.

In short, opening a new window by running a roxterm command should now set the cwd the way you want, but I can't change what happens to it when using the New Window/Tab menu items. Please checkout the latest svn.

Original comment by: realh

from roxterm.