GNU bug report logs - #16692
24.2; nlinum version 1.2 does not work correctly with indirect buffers

Previous Next

Full log

Message #20 received at 16692 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Mark Lillibridge <mdl <at> alum.mit.edu>
Cc: 16692 <at> debbugs.gnu.org
Subject: Re: 24.2;
 nlinum version 1.2 does not work correctly with indirect buffers
Date: Tue, 18 Feb 2014 12:14:40 -0500

>     Hit enter multiple times; observe that line numbers for the new
>     lines appear in the original buffer but not the indirect buffer you
>     are currently in.  This is a bug: line numbers should be present for
>     every line in both buffers.
    
The core of the problem is that jit-lock relies on text-properties,
i.e. data shared between the indirect buffers, but is run "per buffer".
This can be seen also when you use two indirect buffers in different
major modes, where the font-lock behavior can be erratic, mixing the
rules of the different major modes.

I installed a patch which prevents activation of jit-lock in indirect
buffers.  In practice this means that nlinum-mode should now work
correctly in the base buffer but will not work at all in the
indirect buffer.
IOW, problem is still present but it fails more cleanly ;-)


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.