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 669668 - Interaction between the file browser plugin and the file chooser dialog
Interaction between the file browser plugin and the file chooser dialog
Status: RESOLVED OBSOLETE
Product: gedit
Classification: Applications
Component: general
3.3.x
Other Linux
: Normal enhancement
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-08 13:42 UTC by Vadim Rutkovsky
Modified: 2020-11-24 09:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Vadim Rutkovsky 2012-02-08 13:42:16 UTC 
Original report: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/685541

- start gedit, open the file browser plugin and show it (F9) on the left side.
- navigate to any directory in file browser
- create a new empty file in gedit, and click on "save".

Result: 'Recently Used' folder is opened
Expected: the file dialog should show the directory I just navigated into in file browser
Comment 1 André Klapper 2012-02-08 17:16:44 UTC 
Highly assuming that this is a gtk+ issue and not a gedit issue.
Comment 2 jessevdk@gmail.com 2012-02-08 21:35:47 UTC 
This is a gedit "issue". The file browser plugin is not integrated in that way in gedit. It basicly means that it will not influence the location where you save a file (or load for that matter). In can understand though why you would expect that behavior, so maybe we can have a look how we can allow this kind of interaction with plugins and the gedit app.
Comment 3 Sébastien Wilmet 2020-11-24 09:58:25 UTC 
Mass-closing of all gedit bugzilla tickets.

Special "code" to find again all those gedit 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.