From: Richard Stallman <rms@gnu.org>
Cc: nickrob@snap.net.nz, lennart.borgman@gmail.com, emacs-devel@gnu.org
Subject: Re: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]
Date: Mon, 08 Jan 2007 19:01:18 -0500 [thread overview]
Message-ID: <E1H44QY-0007GD-Vy@fencepost.gnu.org> (raw)
In-Reply-To: <45A253B8.6060803@swipnet.se> (message from Jan Djärv on Mon, 08 Jan 2007 15:22:48 +0100)
Yes there is a reason. Compilation mode uses previous-single-property-change
to scan backwards to find the correct position to go to. But if a line begins
at buffer start, there is no property change and
previous-single-property-change return nil.
It would be easy to fix the code to DTRT at the start of the buffer.
Why not make it more robust?
next prev parent reply other threads:[~2007-01-09 0:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 5:32 [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer] Richard Stallman
2007-01-08 7:59 ` Jan Djärv
2007-01-08 8:35 ` Nick Roberts
2007-01-08 9:05 ` Jan Djärv
2007-01-08 11:11 ` Lennart Borgman (gmail)
2007-01-08 14:22 ` Jan Djärv
2007-01-08 14:35 ` Lennart Borgman (gmail)
2007-01-08 15:15 ` Stefan Monnier
2007-01-08 17:37 ` Jan Djärv
2007-01-09 0:01 ` Richard Stallman [this message]
2007-01-08 15:14 ` Bug reporting (was: [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer]) Stefan Monnier
2007-01-08 17:26 ` Bug reporting Lennart Borgman (gmail)
2007-01-11 4:05 ` [lennart.borgman.073@student.lu.se: compilation-previous-error fails if first error is at start of buffer] Nick Roberts
2007-01-18 21:33 ` Nick Roberts
2007-01-09 0:00 ` Richard Stallman
2007-01-09 1:27 ` Nick Roberts
2007-01-08 13:43 ` Chris Moore
-- strict thread matches above, loose matches on Subject: below --
2006-12-31 22:13 Richard Stallman
2006-12-25 0:42 Richard Stallman
2006-12-17 5:37 Richard Stallman
2007-01-19 2:33 ` Chong Yidong
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1H44QY-0007GD-Vy@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=nickrob@snap.net.nz \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.