After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 697787 - Cloning a profile named "foo" gives you two "foo" profiles
Cloning a profile named "foo" gives you two "foo" profiles
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: Profiles
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on: 774710
Blocks:
 
 
Reported: 2013-04-11 12:41 UTC by Baptiste Mille-Mathias
Modified: 2018-03-11 17:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Baptiste Mille-Mathias 2013-04-11 12:41:54 UTC 
I have a profile "default", that I cloned, which gave me two "default" profiles, which is a little little misleading.
Perhaps the new-one should call "$profile_name clone" or user should be asked to named the new created terminal straight-away.
Comment 1 Adam Dingle 2013-05-19 20:51:17 UTC 
I agree this is a bit a bit unfortunate.
Comment 2 Christian Persch 2013-05-19 21:28:33 UTC 
Normally the profile preferences dialogue is shown directly afterwards (that this hasn't happened in comment 0 was a bug that's since fixed), with the visible name field focused.
Comment 3 Adam Dingle 2013-05-21 11:21:41 UTC 
(In reply to comment #2)
> Normally the profile preferences dialogue is shown directly afterwards (that
> this hasn't happened in comment 0 was a bug that's since fixed), with the
> visible name field focused.

That's fine, but I still think it's confusing that the new profile has the same name as the old, especially when its name is "Default" as it is likely to be.  I'd suggest either (a) clearing the "Profile name" field in the new profile so that the user must name it explicitly, or (b) appending a suffix such as "(2)" to the name, which would make it clearer what's going on.
Comment 4 Christian Persch 2018-03-11 17:56:48 UTC 
Fixed by the unified prefs dialogue.