From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#25987: 25.2; support gcc fixit notes Date: Thu, 15 Oct 2020 14:23:05 +0000 Message-ID: References: <87lgsj1jle.fsf@tromey.com> <1521218887.2913.237.camel@redhat.com> <83muz7pyde.fsf@gnu.org> <83o8lf9p68.fsf@gnu.org> <26f277bb345f10efe6340ac4074960905064fc97.camel@redhat.com> <83362i2nul.fsf@gnu.org> <83mu0ny4ru.fsf@gnu.org> Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6392"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 25987@debbugs.gnu.org, David Malcolm To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 15 16:24:10 2020 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 1kT4As-0001aS-K6 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Oct 2020 16:24:10 +0200 Original-Received: from localhost ([::1]:48738 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kT4Ar-0003T3-LN for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Oct 2020 10:24:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35256) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kT4Ak-0003Sa-UG for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 10:24:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44591) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kT4Ak-0006Hf-KT for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 10:24:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kT4Ak-0007as-FE for bug-gnu-emacs@gnu.org; Thu, 15 Oct 2020 10:24:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Andrea Corallo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 15 Oct 2020 14:24:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 25987 X-GNU-PR-Package: emacs Original-Received: via spool by 25987-submit@debbugs.gnu.org id=B25987.160277179329102 (code B ref 25987); Thu, 15 Oct 2020 14:24:02 +0000 Original-Received: (at 25987) by debbugs.gnu.org; 15 Oct 2020 14:23:13 +0000 Original-Received: from localhost ([127.0.0.1]:56137 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kT49x-0007ZK-JG for submit@debbugs.gnu.org; Thu, 15 Oct 2020 10:23:13 -0400 Original-Received: from mab.sdf.org ([205.166.94.33]:50164 helo=ma.sdf.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kT49w-0007ZD-PI for 25987@debbugs.gnu.org; Thu, 15 Oct 2020 10:23:13 -0400 Original-Received: from akrl by ma.sdf.org with local (Exim 4.92) (envelope-from ) id 1kT49p-0001PB-Mp; Thu, 15 Oct 2020 14:23:05 +0000 In-Reply-To: <83mu0ny4ru.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Oct 2020 16:53:25 +0300") 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:190584 Archived-At: Eli Zaretskii writes: >> From: David Malcolm >> Cc: 25987@debbugs.gnu.org >> Date: Wed, 14 Oct 2020 18:43:33 -0400 >> >> In his email, Andrea suggests outputting to a file. How would >> that work? It strikes me as making it difficult to associate the >> output from stderr with that to the file, or would the output to the >> file need to replace that from stderr (in which case what about lines >> of output from "make"? or other build system messages, etc). > > I'm not sure how a separate file comes into this. Aren't we talking > about the "normal" GCC diagnostic output, just augmented by hints? > That has the advantage that it is also human-readable, and could help > the user make changes other than accepting the hints. I explained this in my last mail on this thread, to make it short using stderr can't work reliably for parallel builds. Maybe we decide that's good enought but has to be considered now as IMO it's a strong limitation. Andrea