From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Mark Lillibridge <mdl@alum.mit.edu>
Cc: 16692@debbugs.gnu.org
Subject: bug#16692: 24.2; nlinum version 1.2 does not work correctly with indirect buffers
Date: Tue, 18 Feb 2014 12:14:40 -0500 [thread overview]
Message-ID: <jwvfvnpr1r0.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87ob2hxuzb.fsf@foil.strangled.net> (Mark Lillibridge's message of "Sat, 08 Feb 2014 11:30:48 -0800")
> 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
next prev parent reply other threads:[~2014-02-18 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 19:30 bug#16692: 24.2; nlinum version 1.2 does not work correctly with indirect buffers Mark Lillibridge
2014-02-08 19:45 ` Eli Zaretskii
2014-02-08 20:01 ` Mark Lillibridge
2014-02-08 20:13 ` Eli Zaretskii
2014-02-08 23:44 ` Alp Aker
2014-03-01 19:57 ` Mark Lillibridge
2014-03-01 20:04 ` Eli Zaretskii
2014-02-18 17:14 ` Stefan Monnier [this message]
2014-02-23 18:49 ` Mark Lillibridge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfvnpr1r0.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=16692@debbugs.gnu.org \
--cc=mdl@alum.mit.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.