GNOME Bugzilla – Bug 75773
Command setting in profile not very useful
Last modified: 2004-12-22 21:47:04 UTC
In GNOME Terminal 2, you can specify a custom command to run instead of the shell for a defined profile, and that's good. The way the feature works is kinda confusing though. I don't think it's clear to the user what happens when he changes the command, and how that affects the terminal. For example, I have set up a profile for ssh'ing to my laptop machine, which specifies ssh as the custom command. Now, to trigger ssh I have to select the ssh profile from the Terminal menu, and then go File -> New Window. Not very intuitive. So, I think we should at least have a "File -> New Window with Profile" command, and also we should have a way to apply the change in the command entry to the current terminals. Or at least there should be an help text explaining that that setting only applies if you open another window with the same profile. Or something.
I think the basic problem is the lack of "new window with profile", there's already a bug in here about adding that, it is required to make the "command" feature useful. Or really to make profiles useful. I don't think killing the current terminal process when you change the command is at all a good idea, so there's some inherent possible confusion, though I think people will figure it out. Suggested improved wording is welcome.
*** This bug has been marked as a duplicate of 74598 ***