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 697248 - external tools: renamed tool retains old alphabetical position
external tools: renamed tool retains old alphabetical position
Status: RESOLVED DUPLICATE of bug 697246
Product: gedit-plugins
Classification: Other
Component: General
git master
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2013-04-04 10:08 UTC by Adam Dingle
Modified: 2019-03-23 20:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2013-04-04 10:08:31 UTC 
When I rename a external tool, it is still positioned in the External Tools menu according to its old name.   In more detail:

1. Create an external tool "First".
2. Restart gedit so that Tools->External Tools is alphabetized (this is necessary due to bug 697246).
3. Rename the tool to "Second".
4. Restart gedit again, then look at the Tools->External Tools menu.  The tool will be positioned as if it were still called "First".
Comment 1 Ignacio Casal Quinteiro (nacho) 2013-04-19 15:43:36 UTC 
This should be fixed now.... Can you check?
Comment 2 Adam Dingle 2013-04-19 16:32:18 UTC 
Unfortunately this is not fixed; the behavior is exactly the same as before, as you'll see if you follow the steps above.

I do see that tools are now staying in alphabetical order in the external tools dialog though (that's half of bug 697246).
Comment 3 Ignacio Casal Quinteiro (nacho) 2013-04-19 16:40:21 UTC 
yeah I meant the dialog... that's the only thing I fixed.
Comment 4 Ignacio Casal Quinteiro (nacho) 2013-04-19 16:42:30 UTC 
Oh right commented in the wrong bug :)
Comment 5 Garrett Regier 2013-06-15 12:06:08 UTC 
This bug is also fixed by the patch to the other bug.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 697246 ***