Bug 907708 - gedit Right Margin is invisible
Summary: gedit Right Margin is invisible
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gtksourceview3
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-02-05 04:00 UTC by Elliott Sales de Andrade
Modified: 2013-02-18 22:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-18 22:48:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Missing right margin (66.84 KB, image/png)
2013-02-05 04:01 UTC, Elliott Sales de Andrade
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 675785 0 None None None Never

Description Elliott Sales de Andrade 2013-02-05 04:00:45 UTC
Description of problem:
The right margin in gedit does not appear.

Version-Release number of selected component (if applicable):
gedit-3.6.2-1.fc18.x86_64

Steps to Reproduce:
1. Open gedit.
2. Open Preferences and enable "Display right margin at column:"
  
Actual results:
No indicator of the right margin, as you can see in the screenshot.

Expected results:
A line at column 80 indicating the right margin should be visible.

Additional info:

Comment 1 Elliott Sales de Andrade 2013-02-05 04:01:12 UTC
Created attachment 693151 [details]
Missing right margin

Comment 2 Elliott Sales de Andrade 2013-02-05 04:02:44 UTC
Also, you can see in the screenshot that the "Highlight current line" functionality does not appear to work either.

Comment 3 Elliott Sales de Andrade 2013-02-05 04:23:25 UTC
Of course, I find the upstream bug after filing this one.

It should be fixed, though for some reason I don't seem to see it in the repos yet. I guess I'll wait a few days.

Comment 4 Elliott Sales de Andrade 2013-02-18 22:48:55 UTC
I believe this is fixes now.


Note You need to log in before you can comment on or make changes to this bug.