unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenneth Zadeck <zadeck@naturalbridge.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 54671@debbugs.gnu.org, "Mattias Engdegård" <mattiase@acm.org>
Subject: bug#54671: 26.3; compilation mode tracking error messages
Date: Sat, 2 Apr 2022 12:40:20 -0400	[thread overview]
Message-ID: <051abb4d-db46-7892-cb6d-07bab35c70cd@naturalbridge.com> (raw)
In-Reply-To: <87lewnh40c.fsf@gnus.org>

I should admit to you that several years ago I was a gcc maintainer and 
in my time doing that, I never saw gcc generate anything like this.   
But I am now writing a different tool and I had forgot the syntax of 
error messages and the internet came back with that page - and it does 
not work in emacs.

What does work fine is to replace the "-" with a "\n" so that each 
file/lineNo is on a separate line.   Then emacs's next error will just 
move you from one context to the next until you find the right place.

As I said in my original post, I am only submitting it, because 
according to GNU specific documentation, this should work.

Thanks

Kenny

On 4/2/22 11:57, Lars Ingebrigtsen wrote:
> Kenneth Zadeck <zadeck@naturalbridge.com> writes:
>
>> There is a page on the web that purports to specify the format of error
>> messages for gnu products. I would have assumed that gnuemacs
>> would have fully implemented this set of standards.
>>
>> https://www.gnu.org/prep/standards/html_node/Errors.html
>>
>> The claim is that
>>
>> "When an error is spread over several files, you can use this format:
>>
>> file1:line1.column1-file2:line2.column2: message"
>>
>> gnuemacs does not seem to understand this in the next error function.
>> It only sees the first file, line. The message
>>
>> =====
>> ../xmltools/XSD11/schemaDriver.xsd:10.1-../xmltools/XSD11/XMLSchema.xsd:86.1-../xmltools/XML/xml.xsd:4:
> Yes, I can't see any attempt to try to parse multi-file error lines in
> compilation-error-regexp-alist-alist (but the `gnu' rule there parses
> this as a single file named
> "../xmltools/XSD11/schemaDriver.xsd:10.1-../xmltools/XSD11/XMLSchema.xsd:86.1-../xmltools/XML/xml.xsd:"
> with an error on line 4, I think).
>
> I'm not sure many programs actually follow the convention stated on that
> URL, but it would be nice to support it, anyway.  But I'm not even sure
> we really support having errors from several files on the same line in
> compilation-mode?  I've added Mattias to the CCs because he was the last
> one to touch the `gnu' bits :-), perhaps he has some comments.  (Or if
> anybody else has an idea, please chime in.)
>





      reply	other threads:[~2022-04-02 16:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 16:25 bug#54671: 26.3; compilation mode tracking error messages Kenneth Zadeck
2022-04-02 15:57 ` Lars Ingebrigtsen
2022-04-02 16:40   ` Kenneth Zadeck [this message]

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=051abb4d-db46-7892-cb6d-07bab35c70cd@naturalbridge.com \
    --to=zadeck@naturalbridge.com \
    --cc=54671@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mattiase@acm.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).