unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Nick Roberts <nickrob@snap.net.nz>, rms@gnu.org, 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 15:22:48 +0100	[thread overview]
Message-ID: <45A253B8.6060803@swipnet.se> (raw)
In-Reply-To: <45A226FF.30507@gmail.com>



Lennart Borgman (gmail) skrev:
> Nick Roberts wrote:
>>  > > If the compilation buffer begins with error lines right at the top:
>>  > >  > > c:/EmacsW32/etc/EmacsW32Util.html:7:5: Warning: <link> 
>> inserting "type"  > > attribute
>>  > > c:/EmacsW32/etc/EmacsW32Util.html:12:19: Warning: <table> lacks 
>>  > > "summary" attribute
>>  > > c:/EmacsW32/etc/EmacsW32Util.html:29:5: Warning: <table> lacks 
>> "summary"  > > attribute
>>  > >  > > then if point is on second line compilation-previous-error 
>> fails.
>>  > >  >  > What is the error message?
>>
>> Warnings and errors are equivalent in the compilation buffer.  I don't 
>> see how
>> Lennart gets error lines right at the top as I always get the 
>> following four
>> lines:
>>
>>     -*- mode: compilation; default-directory: "~/" -*-
>>     Compilation started at Mon Jan  8 21:22:48
>>
>>     `command used for my compilation'
> 
> 
> The output is from a library not included in Emacs (actually a version 
> of tidy.el). The output does not have the lines above at the beginning. 
> It would be rather inconvenient if it had, but maybe those line still 
> should be there for some reason?
> 

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.

I think you should modify your library to add an empty line at the top, or 
maybe some informative text.

	Jan D.

  reply	other threads:[~2007-01-08 14:22 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 [this message]
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
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

  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=45A253B8.6060803@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    --cc=rms@gnu.org \
    /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).