From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 18035@debbugs.gnu.org, lionel.hry@gmail.com
Subject: bug#18035: Linum-mode + org-indent-mode results in graphical bug
Date: Thu, 17 Jul 2014 18:21:33 +0300 [thread overview]
Message-ID: <83fvi06mf6.fsf@gnu.org> (raw)
In-Reply-To: <87ha2hrx0p.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 18035@debbugs.gnu.org, Lionel Henry <lionel.hry@gmail.com>
> Date: Wed, 16 Jul 2014 20:14:46 +0200
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > > > Activating both linum-mode and org-indent-mode will cause several
> > > > graphical glitches in the current line.
> > > > See
> > > > http://lists.gnu.org/archive/html/emacs-orgmode/2011-01/msg01204.html
> > >
> > > That discussion provides no reproducible recipe.
>
> But I think I found something that is related (before-string overlays
> vs. text properties) and is reproducible for emacs -Q:
It's specific to invisible property, not just any property, and also
requires that another text property starts exactly where the invisible
property ends.
I'm not sure this is the same problem as reported by the OP, so it
probably should have been reported as a separate bug (merging them
later is easy).
> - visit a file under version control (I tried a git controlled file here)
> - M-x vc-annotate
> - v (i.e. vc-annotate-toggle-annotation-visibility)
> - M-x linum-mode
>
> ==> all lines but one loose their coloring. Those lines that are still
> colored loose their line number.
>
> nlinum-mode behaves similarly.
Fixed in revision 117382 on the emacs-24 branch.
next prev parent reply other threads:[~2014-07-17 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14B03A2E-7F4C-4329-8E0F-70A31D9C28E6@gmail.com>
2014-07-16 16:38 ` bug#18035: Linum-mode + org-indent-mode results in graphical bug Eli Zaretskii
[not found] ` <83sim16yz9.fsf@gnu.org>
2014-07-16 17:16 ` Lionel Henry
2014-07-16 18:02 ` Michael Heerdegen
[not found] ` <87lhrtrxl1.fsf@web.de>
2014-07-16 18:14 ` Michael Heerdegen
2014-07-17 15:21 ` Eli Zaretskii [this message]
[not found] ` <83fvi06mf6.fsf__22788.3604042747$1405610578$gmane$org@gnu.org>
2014-07-17 23:36 ` Michael Heerdegen
2014-07-26 15:03 ` Lionel Henry
[not found] ` <AAFE2358-C3A2-4294-AAA6-4A604F2B706C@gmail.com>
2014-07-26 15:11 ` Lionel Henry
2014-07-26 15:36 ` Eli Zaretskii
[not found] ` <83a97wi13r.fsf@gnu.org>
2014-07-26 15:53 ` Lionel Henry
[not found] ` <B5583174-4C99-4EA4-BD72-4FD86BB462CB@gmail.com>
2014-07-28 13:11 ` Eli Zaretskii
2014-07-28 13:14 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83fvi06mf6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18035@debbugs.gnu.org \
--cc=lionel.hry@gmail.com \
--cc=michael_heerdegen@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).