emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lionel Henry <lionel.hry@gmail.com>
Cc: michael_heerdegen@web.de, 18035@debbugs.gnu.org
Subject: bug#18035: Linum-mode + org-indent-mode results in graphical bug
Date: Sat, 26 Jul 2014 18:36:08 +0300	[thread overview]
Message-ID: <83a97wi13r.fsf__21863.1160249517$1406389063$gmane$org@gnu.org> (raw)
In-Reply-To: <AAFE2358-C3A2-4294-AAA6-4A604F2B706C@gmail.com>

> From: Lionel Henry <lionel.hry@gmail.com>
> Date: Sat, 26 Jul 2014 17:03:49 +0200
> Cc: 18035@debbugs.gnu.org,
>  michael_heerdegen@web.de
> First create a .org file and put the rainbow-delimiters package in your load path.
> Then execute this :
> (progn
>   (require 'rainbow-delimiters)
>   (rainbow-delimiters-mode)
>   (linum-mode)
>   (org-indent-mode))
> Then enter this in the org file :
> * head 1
> ** head 2
> line 1
> line 2
> Line 2 is important, without it the bug does not happens. Now modify head 2.
> The linum number will disappear and the whole active line will shift to the left.
> So it's an interaction between linum, org-indent-mode, and rainbow-delimiters-mode.


AFAICS, rainbow-delimiters-mode uses the JIT Font Lock machinery to do
its job, which might conflict with org-indent's usage of an idle timer
and/or fail to trigger linum-mode's update on that line.  When I
modify the "head 2" line, the line number is still visible, but then
about a second later the line gets re-indented and the line number

I suggest that you report this to the developers of org-indent and
rainbow-delimiters-mode, and ask them to debug this.  If their
conclusion is that this is a core Emacs problem, please get back here
and report the details.

  parent reply	other threads:[~2014-07-26 15:37 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
     [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 [this message]
     [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:

  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='83a97wi13r.fsf__21863.1160249517$1406389063$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --cc=18035@debbugs.gnu.org \
    --cc=lionel.hry@gmail.com \
    --cc=michael_heerdegen@web.de \


* 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


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).