[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15841: Display bugs with cache-long-lines non-nil

From: Eli Zaretskii
Subject: bug#15841: Display bugs with cache-long-lines non-nil
Date: Sat, 09 Nov 2013 10:18:28 +0200

Redirected to a new bug report, please use this one in the future.

> From: Nathan Trapuzzano <address@hidden>
> Cc: Eli Zaretskii <address@hidden>,  Michael Heerdegen <address@hidden>,  
> address@hidden,  address@hidden
> Date: Fri, 08 Nov 2013 14:07:44 -0500
> Stefan Monnier <address@hidden> writes:
> >> I wonder if we should simply turn it on by default, and leave it
> >> there.  That way, any bugs that it exposes will be flushed out very
> >> quickly.  Stefan?
> >
> > Let's try it.
> 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]