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 774620 - Let's call the default profile "Default"?
Let's call the default profile "Default"?
Status: RESOLVED OBSOLETE
Product: gnome-terminal
Classification: Core
Component: Profiles
git master
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on: 774710
Blocks:
 
 
Reported: 2016-11-17 14:27 UTC by Egmont Koblinger
Modified: 2021-06-10 21:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Egmont Koblinger 2016-11-17 14:27:44 UTC 
Not sure if I recall correctly, but wasn't the default profile previously named "Default"?

Currently the default (only) profile is called "Unnamed" on a brand new user account.

I think "Default" is a much better name as soon as one creates another profile (and until then it really doesn't matter), to me it sounds silly to have a profile with a proper name and another one called "Unnamed". What do you think?
Comment 1 Egmont Koblinger 2018-01-02 09:05:59 UTC 
I'm not so sure about the suggested name "Default" anymore.

The term "default" is overloaded:

- It could mean "the profile used for new terminals", but then it's confusing that you can set another profile as the default and then "Default" is not the default.

- It could also mean g-t's default settings, that is, the ones that brand new (not cloned) profiles get. Then again it's confusing that you can alter its settings and it's still called "Default".

So I actually like how the current UI avoids using this term here.

I still don't quite like "Unnamed" though... Just not sure what would be a better one.
Comment 2 GNOME Infrastructure Team 2021-06-10 21:10:32 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/7708.