GNU bug report logs - #15841
Display bugs with cache-long-lines non-nil

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#15841: closed (Re: bug#15841: Display bugs with
 cache-long-lines non-nil)
Date: Mon, 18 Nov 2013 16:33:04 +0000

[Message part 1 (text/plain, inline)]

Your bug report

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

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 15841 <at> debbugs.gnu.org.

-- 
15841: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15841
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andy Moreton <andrewjmoreton <at> gmail.com>,
 Stephen Berman <stephen.berman <at> gmx.net>
Cc: 15841-done <at> debbugs.gnu.org
Subject: Re: bug#15841: Display bugs with cache-long-lines non-nil
Date: Mon, 18 Nov 2013 18:32:05 +0200

> From: Stephen Berman <stephen.berman <at> gmx.net>
> Cc: 15841 <at> debbugs.gnu.org
> Date: Fri, 15 Nov 2013 19:05:42 +0100
> 
> Initial tests succeeded: `i' in Dired works as expected and there is no
> infloop or display oddities.  I'll report back if any problems crop up
> on further use.  Otherwise, thanks for fixing this!

No further problems, so I committed the changes as trunk revision
115138, and I'm closing this bug.

[Message part 3 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Nathan Trapuzzano <nbtrap <at> nbtrap.com>
Cc: bug-gnu-emacs <at> gnu.org
Subject: 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 <nbtrap <at> nbtrap.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  Michael Heerdegen <michael_heerdegen <at> web.de>,  15797 <at> debbugs.gnu.org,  kjambunathan <at> gmail.com
> Date: Fri, 08 Nov 2013 14:07:44 -0500
> 
> Stefan Monnier <monnier <at> iro.umontreal.ca> 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.

Previous Next

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