When saving file, gedit reset tab width to 8 characters

Bug #490772 reported by Lupi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
Undecided
Unassigned
gedit
Fix Released
Medium
gedit (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

In gedit, when you set tab width to 4 or 2 characters and then save the file, the tab width resets to 8.
It shouldn't change it until I close the program. Or even better, save the tab width for future gedit executions

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

this is known upstream and supposed to be fixed on karmic, could you try the same if is not fixed comment on the upstream bts? https://bugzilla.gnome.org/show_bug.cgi?id=569849 ; Thanks.

Changed in gedit (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Bill Zimmerly (billzimmerly) wrote :

I will add my complaint as well. Every time I start a gedit session, it starts in 8/tab mode whereas I prefer 2/spaces as my default.

It's easy to click the 2/spaces setting in the status line - but why won't it remember this for my next editing session?

I have the default set to 2/spaces in Edit / Preferences / Editor, but this doesn't seem to make any difference whatsoever!

Please fix this annoyance. (Thank you!)

- Bill

Revision history for this message
Vish (vish) wrote :

Thank you for bringing this bug to our attention. However, a paper cut should be a small usability issue, in the default Ubuntu install, that affects many people and is quick and easy to fix. So this bug can't be addressed as part of this project.

- This is a bug not a papercut.
For further information about papercuts criteria, please read https://wiki.ubuntu.com/PaperCut.

Don't worry though, this bug has been marked as "Invalid" only in the papercuts project.

Changed in hundredpapercuts:
status: New → Invalid
Revision history for this message
Lesmana Zimmer (lesmana) wrote :

is this a duplicate of bug #340056?

Revision history for this message
Sense Egbert Hofstede (sense) wrote :

Probably, but lets leave that bug for what it is since it's marked as Fix Released and therefore not getting in anyone's way. Thank you for noticing, though!

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Well, also the upstream bug is marked as fix released in may 2009. should we open another upstream bug?

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Can you try to disable the "modelines" gedit plugin? It seems I don't have this problem anymore

Revision history for this message
Michael Herold (michaeljherold) wrote :

@Nicolò Chieffo
I have this problem and do not have the ``modelines'' gedit plugin enabled, so it seems that it's not related to that.

I've been using gedit for several hours every day for the past week and have only noticed it in the last hour. It is also intermittent in its manifesting, as it only occurs with some files. For instance, I have two Python files and a plaintext file that are open right now and it is only occurring in one of the Python files.

Aha! While typing this reply, I tested something. My indentation was messed up in one function in the file that was giving me trouble (i.e. the indentation in that function was 8 spaces, while I want a setting of 8 spaces.) When I reset its indentation to the proper level (i.e. 4 spaces) and re-saved the file, it kept the 4 spaces setting. So it seems that gedit infers the setting upon save.

I'm not sure if this is related to the bug, but I thought I would include it for reference, in case this is the root of the problem for the original reporter.

Changed in gedit:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Can we close this bug? Is there anyone which is still affected?

Revision history for this message
Vish (vish) wrote :

Thanks for following up. I can confirm this is fixed in Lucid.

 For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in gedit (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: Triaged → Fix Released
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.