GNU bug report logs - #197
next-error wrong position in target file

Previous Next

Package: emacs;

Reported by: Kevin Ryde <user42 <at> zip.com.au>

Date: Wed, 7 May 2008 23:45:03 UTC

Severity: normal

Merged with 216

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 197 in the body.
You can then email your comments to 197 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>:
bug#197; Package emacs. Full text and rfc822 format available.

Acknowledgement sent to Kevin Ryde <user42 <at> zip.com.au>:
New bug report received and forwarded. Copy sent to Emacs Bugs <bug-gnu-emacs <at> gnu.org>. Full text and rfc822 format available.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Kevin Ryde <user42 <at> zip.com.au>
To: bug-gnu-emacs <at> gnu.org
Subject: next-error wrong position in target file
Date: Thu, 08 May 2008 09:37:54 +1000
[Message part 1 (text/plain, inline)]
In Emacs 22.2, the first `next-error' in certain circumstances goes to
the wrong error line in the target file.  With the dummy file foo.txt
below, and on a 50 line console,

    emacs -Q foo.txt
    C-v               # page down in foo.txt
    C-x b Ret         # back to *scratch* buffer
    M-x compile
    echo 'foo.txt:''150: an error here'
    C-x `             # next-error

    => goes to foo.txt with point at line 56

The echo simply produces a compilation buffer claiming an error at
foo.txt line 150, but then next-error goes to line 56.  On a different
size terminal or under X you get a different wrong position, like line
45 or 24.

The recipe above is rather specific, there's all sorts of ways it works
correctly.  If you don't scroll-up, or if you leave foo.txt the current
buffer, then it's fine.  I've struck this on various occasions without
ever being able to reproduce it, since a second try in the same session
goes ok!  My recent-ish build of the current emacs cvs head still seems
to have the problem too, whatever it is.



In GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.3)
 of 2008-04-11 on raven, modified by Debian
configured using `configure  '--build=i486-linux-gnu' '--host=i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var/lib' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs22:/etc/emacs:/usr/local/share/emacs/22.2/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/22.2/site-lisp:/usr/share/emacs/site-lisp:/usr/share/emacs/22.2/leim' '--with-x=yes' '--with-x-toolkit=gtk' '--with-toolkit-scroll-bars' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -g -O2''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_AU
  locale-coding-system: iso-8859-1
  default-enable-multibyte-characters: t


[foo.txt (text/plain, attachment)]

Merged 197 216. Request was from Jason Rumney <jasonr <at> gnu.org> to control <at> emacsbugs.donarmstrong.com. (Sun, 11 May 2008 01:25:04 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <don <at> donarmstrong.com> to internal_control <at> emacsbugs.donarmstrong.com. (Tue, 26 Aug 2008 14:24:03 GMT) Full text and rfc822 format available.

This bug report was last modified 16 years and 298 days ago.

Previous Next


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