> Is this not a bug then? Shall I mark it invalid? However, it is still odd that the jaunty version did not depend on the profile file being there.
I think we should leave this bug open until somebody competent (i.e. shell expert) can comment on the issue. Technically, in old versions (jaunty) nautilus-open-terminal set the working directory to the desired target directory, followed by running your terminal. In more recent versions (karmic), nautilus-open-terminal calls foo-terminal -x "cd $target_directory && sh -l". The reason for this change was that with old versions, when opening a terminal for directories on removable media, one could not eject the medium before closing the terminal because the working directory of the terminal binary was set to a mounted path on the media. However, the "sh -l" call with the login flag was just blindly copied from the remote SSH code, which calls ssh <target-specifier> "cd $remote_target_directory && sh -l". There may be reasons to call "sh" without any flags, or with the "-i" flag, or even with "-i -l", depending on the meaning of interactivity and login shells - but I don't want to change anything unless a shell expert explains the flags, and the correct call. I didn't find it properly explained in the bash man page nor in Wikipedia, so I'm somewhat stuck. Please note that even the (very old) eel code in Nautilus seems to call third-party terminals (everything except gnome-terminal) with the -ls flags which also seems to spawn a login shell. However, when calling gnome-terminal without any parameters it seems to spawn an interactive shell. In other words, GNOME has suffered from an inconsistent terminal opening behavior for ages. -- .bashrc is not executed when terminal is opened through nautilus-open-terminal https://bugs.launchpad.net/bugs/448337 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
