Path to file being edited does not appear in title bar

Bug #457126 reported by tiggsy
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

1) Jaunty Jackelope i386
2) gedit 2.26.1
3) In the previous version (supplied with Hardy Heron), the path to the file being edited appeared in the top bar. This was useful when editing 2 files with the same name from different places - which I do frequently. For instance, I might have the index.php file for one site open as a template for a similar routine on another site, which is just being implemented.
4) The bar now just shows the file name, followed by the disk it's on in brackets - eg temp.html (sdb)

How do i restore this functionality, or will i have to wait for a bugfix? It's going to make my work much more difficult until it's sorted.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gedit
Package: gedit 2.26.1-0ubuntu1
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
Uname: Linux 2.6.28-15-generic i686

Revision history for this message
tiggsy (frann-leach) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

that works fine for me on karmic, the title bar appear as : File (~/path/) - gedit ; probably you have something broken on your profile , could you try the same with a new user there? thanks.

Changed in gedit (Ubuntu):
importance: Undecided → Low
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
Revision history for this message
tiggsy (frann-leach) wrote : Re: [Bug 457126] Re: Path to file being edited does not appear in title bar

Sure, if you will explain how.

Pedro Villavicencio wrote:
> that works fine for me on karmic, the title bar appear as : File
> (~/path/) - gedit ; probably you have something broken on your profile ,
> could you try the same with a new user there? thanks.
>
> ** Changed in: gedit (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: gedit (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: gedit (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
>

Revision history for this message
Pedro Villavicencio (pedro) wrote :

if i explain what? how to create a new user? just to go System -> Administration -> Users and Groups there's an option to create a new user, just login with that after the creation and test the same there.

Revision history for this message
tiggsy (frann-leach) wrote :

Hi Pedro

Thanks for that. After enabling Users and Groups (which for some reason
was disabled in the menus) I did what you said, and sure, it works for
files on the home disk. And when I came back to my normal user, I see
that it works in my user too BUT ONLY FOR FILES ON THE "HOME" disk.

All my programming and internet source files are on a separate drive:
sdb. I don't have room for them on the home drive. All I get in the
title bar is (sdb) as the address, no matter where on that disk the file
resides. In Hardy, i got a full path name. So this appears to be a bug
affecting files on drives other than the home drive.

frann

Pedro Villavicencio wrote:
> if i explain what? how to create a new user? just to go System ->
> Administration -> Users and Groups there's an option to create a new
> user, just login with that after the creation and test the same there.
>
>

Revision history for this message
glinsvad (glinsvad) wrote :

I can confirm the reported behavior. If I edit a file on my home partition, the full path is listed with the ~ shorthand, however, if I copy the file to /media/disk (or a subfolder there) and edit it from there, only the disk label is shown. If I insert a peripheral like an unlabeled USB drive, it gets mounted e.g. on /media/07F1-0026 but gedit shows "8.2 GB Filesystem", which is even less helpful when you're mostly on the command line.

Why is this bug marked as incomplete? What more information do you need from us?

I would appreciate that the importance be bumped from "low" as this is making it completely unfeasible to use gedit as a lightweight IDE, which was (IMO) one of its strong points. With Python being so important to Ubuntu, you'd think that editing hundreds of __init__.py file without access to the full path would be more of a priority issue.

Architecture: amd64
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gedit
Package: gedit 2.28.0-0ubuntu2
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
Uname: 2.6.31-22-generic x86_64

ben (bentaieb)
Changed in gedit (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Can you reporduce this ing gedit 3.x.x version? Now it seems to display correctly, e.g. "autorun.inf [Read Only] Ubuntu 12.04 LTS i386 /media/Ubuntu 12.04 LTS i386", so the file from "/media/Ubuntu 12.04 LTS i386" is being edited

Changed in gedit (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
glinsvad (glinsvad) wrote :

No this issue isn't reproducable with gedit 3.2.x but now it shows redundant information when the drive label is identical to the mount point e.g. if a volume labeled 'backup' is mounted in /media/backup and you edit /media/backup/important.txt, gedit displays "important.txt (backup /media/backup)". I suppose it's better than the alternative...

Architecture: amd64
DistroRelease: Ubuntu 11.10
ExecutablePath: /usr/bin/gedit
Package: gedit 3.2.3-0ubuntu0.1
ProcEnviron:
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
SourcePackage: gedit
Uname: 3.0.0-16-generic x86_64

Bruce Tarro (cydizen)
Changed in gedit (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.