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 699002 - file browser: remove Delete from context menu
file browser: remove Delete from context menu
Status: RESOLVED OBSOLETE
Product: gedit-plugins
Classification: Other
Component: General
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on: 688421
Blocks:
 
 
Reported: 2013-04-26 21:31 UTC by Adam Dingle
Modified: 2020-11-24 10:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2013-04-26 21:31:55 UTC 
Today, the file browser has both Delete and Move to Trash in its context menu.  Nautilus's context menu has both these commands if I've checked the preference "Include a Delete command that bypasses Trash" in Nautilus, but the gedit file browser shows both these commands even if this preference is unchecked.

I think that gedit should show the Delete command only (a) when that preference is checked, or (b) never.  Either way is fine with me.
Comment 1 Ignacio Casal Quinteiro (nacho) 2013-04-27 09:39:01 UTC 
yes, this is a regression from the port to gmenumodel. We are waiting for a glib bug to be fixed to do this.
Comment 2 Adam Dingle 2013-04-27 09:39:41 UTC 
Ah I see.  Which glib bug?  Can you link to it here?
Comment 3 Adam Dingle 2013-04-27 09:45:04 UTC 
Thanks.  A GTK bug, actually.
Comment 4 Sébastien Wilmet 2020-11-24 10:17:42 UTC 
Mass-closing of all gedit-plugins bugzilla tickets.

Special "code" to find again all those gedit-plugins bugzilla tickets that were open before the mass-closing:

2bfe1b0590a78457e1f1a6a90fb975f5878cb60064ccfe1d7db76ca0da52f0f3

By searching the above sha256sum in bugzilla, the gedit contributors can find again the tickets. We may be interested to do so when we work on a specific area of the code, to at least know the known problems and possible enhancements.

We do this mass-closing because bugzilla.gnome.org is being replaced by gitlab.gnome.org.