From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Kenneth Zadeck Newsgroups: gmane.emacs.bugs Subject: bug#54671: 26.3; compilation mode tracking error messages Date: Sat, 2 Apr 2022 12:40:20 -0400 Message-ID: <051abb4d-db46-7892-cb6d-07bab35c70cd@naturalbridge.com> References: <1e008d6d-a6ec-fc12-5144-d10c3281e55a@naturalbridge.com> <87lewnh40c.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21018"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Cc: 54671@debbugs.gnu.org, Mattias =?UTF-8?Q?Engdeg=C3=A5rd?= To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Apr 02 20:09:11 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1naiBT-0005GU-B5 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 02 Apr 2022 20:09:11 +0200 Original-Received: from localhost ([::1]:45236 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1naiBR-00006U-D0 for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 02 Apr 2022 14:09:09 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:59220) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1naiBK-00006A-1y for bug-gnu-emacs@gnu.org; Sat, 02 Apr 2022 14:09:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:52930) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1naiBJ-0002Yd-Pl for bug-gnu-emacs@gnu.org; Sat, 02 Apr 2022 14:09:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1naiBJ-00047t-LA for bug-gnu-emacs@gnu.org; Sat, 02 Apr 2022 14:09:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Kenneth Zadeck Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 02 Apr 2022 18:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 54671 X-GNU-PR-Package: emacs Original-Received: via spool by 54671-submit@debbugs.gnu.org id=B54671.164892293215845 (code B ref 54671); Sat, 02 Apr 2022 18:09:01 +0000 Original-Received: (at 54671) by debbugs.gnu.org; 2 Apr 2022 18:08:52 +0000 Original-Received: from localhost ([127.0.0.1]:46827 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1naiBA-00047V-1q for submit@debbugs.gnu.org; Sat, 02 Apr 2022 14:08:52 -0400 Original-Received: from mail-qv1-f52.google.com ([209.85.219.52]:39792) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nagnb-0001tw-Lz for 54671@debbugs.gnu.org; Sat, 02 Apr 2022 12:40:28 -0400 Original-Received: by mail-qv1-f52.google.com with SMTP id kd21so4311959qvb.6 for <54671@debbugs.gnu.org>; Sat, 02 Apr 2022 09:40:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=naturalbridge-com.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=mTX7YcDpmfeU040xhvpvkUuqeks/UMO8Rcxpt7qifiM=; b=OXrEstR+b50dKsnr7YiXX7003vxvKQ3+1n8Vjco65plOPsnDMMsHCknSp/IY57lc1q NXHTQMtnvlRtVAb/s7pGB8Av09Vmz762WCpV0Ug120dNKbiQn3lzMHQxpjVm+0nVELk0 ESarBDZ/qTt5Ot1zhQA0HJApAoBIHW0gIK7kKOkptCiBu2GjRUe++/8+SHs3rrnvnIEg i/V0BVeQSSTNO0yRMWDXR2AxNXC6rhD8MoVigZNllIbDyo8XC+qCf6gAiKdG5Im3LjvO bd+DqC8MW9uBcADMKN4hlq/lNrUqBciFT6EaihX9J/+v+hUBq6vDeD8myt/CaCWIWzj0 Tz6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=mTX7YcDpmfeU040xhvpvkUuqeks/UMO8Rcxpt7qifiM=; b=k7xURBkuil6O9fWVID89qtklsyvJ3+nmPnpufAuQUqKaXqyichTlasANgpFh8KGfAw QlEmb6Va3xnJ5Z67gLakS1KJ0eI/sa+MmyUHbosYJXPa+4mTtn36Pp7iIts+mXMOsVj5 Y+BnKiSslPEoj+sCWSMSZoH0jkrG2pA3YbehwoFOQMIiTxNEhjd8BFZMVOwJ2IuP3rgt 8V2fr5jdct7iGHXWIxgVsq/JXzKavMenpf/lMx5FPLG8c6Qxs8ClZLTF0A8e+SjTgAn5 efHWCGjO1+y4TJpcHRCzqvuNXqlWMcal5ZcSmbNeJPXSF8PAkACijZOrPWb1mSE1tLXS GKvQ== X-Gm-Message-State: AOAM530JUvocE3E2qq4VxEGqWw7aaLU2CP1LdJsgGU5SPzOYhfmos7bm 2yb4bfmbqsGI05j33v/iE1o2yA== X-Google-Smtp-Source: ABdhPJye8mtOL51n8qERi8Wg8eQ5RN61+6LE7iPSqOiZRk8Az3PLgwH/VUm323tz4kJ07/ocZ7OBgw== X-Received: by 2002:a05:6214:b6d:b0:440:d18b:b7c3 with SMTP id ey13-20020a0562140b6d00b00440d18bb7c3mr12165066qvb.103.1648917622021; Sat, 02 Apr 2022 09:40:22 -0700 (PDT) Original-Received: from [192.168.1.14] (pool-108-41-13-176.nycmny.fios.verizon.net. [108.41.13.176]) by smtp.gmail.com with ESMTPSA id v3-20020a05622a014300b002e1dcd4cfa9sm4482917qtw.64.2022.04.02.09.40.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 02 Apr 2022 09:40:21 -0700 (PDT) Content-Language: en-US In-Reply-To: <87lewnh40c.fsf@gnus.org> X-Mailman-Approved-At: Sat, 02 Apr 2022 14:08:50 -0400 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:229299 Archived-At: 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 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.) >