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 317962 - Path bar and side pane should not show [home][Home]
Path bar and side pane should not show [home][Home]
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: Sidebar
2.12.x
Other All
: High normal
: 2.12.x
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 311340 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-10-04 20:47 UTC by Federico Mena Quintero
Modified: 2005-12-18 02:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12

Attachments
nautilus-consistent-home-folder-name.diff (1.81 KB, patch)
2005-10-04 21:04 UTC, Federico Mena Quintero 		none Details | Review

Description Federico Mena Quintero 2005-10-04 20:47:56 UTC 
I just committed a patch to GTK+ so that both the file chooser's path bar and
the shortcuts bar won't show "Home", but rather the actual folder name for your
$HOME.  This nicer as you don't get [/][home][Home] in the path bar, and it's
also what MacOS does :)

Attached is a patch to make Nautilus do the same thing, for consistency.
Comment 1 Federico Mena Quintero 2005-10-04 21:04:06 UTC 
Created attachment 53034 [details] [review]
nautilus-consistent-home-folder-name.diff
Comment 2 Christian Neumair 2005-10-07 00:09:27 UTC 
Confirming. Please also send the patch to nautilus-list for review.
Comment 3 Federico Mena Quintero 2005-12-01 19:47:49 UTC 
Committed to HEAD per Alex's approval.

2005-12-01  Federico Mena Quintero  <federico@ximian.com>

	Fixes bug #317962:

	* src/nautilus-pathbar.c (get_dir_name): Don't special-case the
	name for $HOME; just let it be the actual display name of the
	folder on disk.

	* src/nautilus-places-sidebar.c (update_places): Likewise, to make
	this consistent.
Comment 4 Martin Wehner 2005-12-18 02:27:51 UTC 
*** Bug 311340 has been marked as a duplicate of this bug. ***