unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Nathan Trapuzzano <nbtrap@nbtrap.com>
Cc: 15797@debbugs.gnu.org, kjambunathan@gmail.com
Subject: bug#15797: 24.3.50; Info: Mention cache-long-scans
Date: Sat, 09 Nov 2013 03:37:49 +0100	[thread overview]
Message-ID: <877gci1erm.fsf@web.de> (raw)
In-Reply-To: <87r4aqww3j.fsf@nbtrap.com> (Nathan Trapuzzano's message of "Fri,  08 Nov 2013 14:07:44 -0500")

Nathan Trapuzzano <nbtrap@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.





  parent reply	other threads:[~2013-11-09  2:37 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 21:35 bug#15797: 24.3.50; Info: Mention cache-long-scans Jambunathan K
2013-11-04  0:36 ` Glenn Morris
2013-11-04  4:41   ` Jambunathan K
2013-11-04 13:10     ` Michael Heerdegen
2013-11-04 14:21       ` Jambunathan K
2013-11-05 16:32       ` Eli Zaretskii
2013-11-05 19:24         ` Stefan Monnier
2013-11-06  4:44           ` Jambunathan K
2013-11-08 10:29             ` Eli Zaretskii
2013-11-08 13:13               ` Jambunathan K
2013-11-08 14:02                 ` Stefan Monnier
2013-11-08 14:08                   ` Jambunathan K
2013-11-08 14:15                 ` Eli Zaretskii
2013-11-08 14:33                   ` Jambunathan K
2013-11-08 15:16                     ` Eli Zaretskii
2013-11-08 10:28           ` Eli Zaretskii
2013-11-08 19:07           ` Nathan Trapuzzano
2013-11-08 20:57             ` Stefan Monnier
2013-11-08 21:36               ` Nathan Trapuzzano
2013-11-08 23:11                 ` Nathan Trapuzzano
2013-11-09  8:33                 ` Eli Zaretskii
2013-11-08 21:18             ` Eli Zaretskii
2013-11-08 21:22               ` Glenn Morris
2013-11-09  2:37             ` Michael Heerdegen [this message]
2013-11-09  8:18             ` bug#15841: Display bugs with cache-long-lines non-nil Eli Zaretskii
2013-11-09  8:31               ` Eli Zaretskii
2013-11-09  8:52                 ` Eli Zaretskii
2013-11-09 11:18                 ` Eli Zaretskii
2013-11-09 14:02                   ` Eli Zaretskii
2013-11-09 21:27                     ` Eli Zaretskii
2013-11-10 18:20                 ` Michael Heerdegen
2013-11-10 18:31                   ` Eli Zaretskii
2013-11-11  3:39                     ` Michael Heerdegen
2013-11-11 16:23                       ` Eli Zaretskii
2013-11-13 23:45                         ` Michael Heerdegen
2013-11-14  3:51                           ` Eli Zaretskii
2013-11-09  8:51               ` Eli Zaretskii
2013-11-11 14:12               ` Stephen Berman
2013-11-11 20:13                 ` Eli Zaretskii
2013-11-11 20:38                   ` Stephen Berman
2013-11-12  0:38                 ` Stephen Berman
2013-11-12 10:03                   ` Stephen Berman
2013-11-12 16:31                     ` Eli Zaretskii
2013-11-12 21:34                       ` Stephen Berman
2013-11-15 16:34                       ` Eli Zaretskii
2013-11-15 18:05                         ` Stephen Berman
2013-11-16 18:53                         ` Andy Moreton
2013-11-16 19:02                           ` Eli Zaretskii
2013-11-18 16:32                           ` Eli Zaretskii
2013-11-06 18:02         ` bug#15797: 24.3.50; Info: Mention cache-long-scans Michael Heerdegen
2013-11-06 18:17           ` Eli Zaretskii
2013-11-06 18:50             ` Michael Heerdegen
2013-11-06 20:46               ` Eli Zaretskii
     [not found]         ` <<87wqkltnmk.fsf@web.de>
     [not found]           ` <<8338n975tf.fsf@gnu.org>
2013-11-06 18:58             ` Drew Adams
2013-11-06 20:56               ` Eli Zaretskii
     [not found] ` <handler.15797.D15797.138352538323812.notifdone@debbugs.gnu.org>
2013-11-04  6:27   ` bug#15797: closed (Re: bug#15797: 24.3.50; Info: Mention cache-long-scans) Jambunathan K
     [not found] <<871u2xf9st.fsf@gmail.com>
     [not found] <"<9jiow9uhoa.fsf"@fencepost.gnu.org>

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877gci1erm.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=15797@debbugs.gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=nbtrap@nbtrap.com \
    /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.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).