GNU bug report logs - #15797
24.3.50; Info: Mention cache-long-scans

Previous Next

Full log

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

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Nathan Trapuzzano <nbtrap <at> nbtrap.com>
Cc: 15797 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>,
 kjambunathan <at> gmail.com
Subject: Re: bug#15797: 24.3.50; Info: Mention cache-long-scans
Date: Sat, 09 Nov 2013 03:37:49 +0100

Nathan Trapuzzano <nbtrap <at> nbtrap.com> writes:

> Sorry I'm late to the party, but this broke linum and nlinum for me,
> using the defaults.  Any time I insert a new line, the line numbers get
> totally messed up--most of them don't even display any more.  And then
> using motion commands sometimes results in really bizarre behavior
> (apparently only with linum/nlinum so far), such as when I do
> forwad-sexp and point goes to the end of some sexp other than the one at
> point.

I see something probably related.  Sometimes, evaluating

  (line-number-at-pos)

at the end of my .emacs (10000 lines) needs over a second.  Doing

  (setq cache-long-scans nil)

immediately fixes this.  Dunno yet how to provoke the problem.


Regards,

Michael.

Previous Next

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