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 586766 - Allow GFilenameCompleter to complete with relative paths
Allow GFilenameCompleter to complete with relative paths
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
2.21.x
Other Linux
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2009-06-23 15:48 UTC by palfrey
Modified: 2018-05-24 11:53 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Adds g_filename_completer_set_path (3.44 KB, patch)
2009-06-24 17:17 UTC, palfrey 		none Details | Review

Description palfrey 2009-06-23 15:48:56 UTC 
Right now, GFilenameCompleter is intended only for absolute paths. For cases like bug 321592, it would be nice to be able to set it to complete from relative locations. This would require a new function to set the relative path, called something like g_filename_completer_set_relative_path (similar pattern to g_filename_completer_set_dirs_only, but with a gchar * uri that could be NULL for going back to non-absolute paths).
Comment 1 palfrey 2009-06-24 17:17:36 UTC 
Created attachment 137326 [details] [review]
Adds g_filename_completer_set_path

g_filename_completer_set_path is just like the g_filename_completer_set_relative_path I proposed in comment #0, but not all the valid paths are relative (absolute ones are fine as well), hence a name change.
Comment 2 GNOME Infrastructure Team 2018-05-24 11:53:48 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/glib/issues/227.