From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: 58653@debbugs.gnu.org
Subject: bug#58653: 29.0.50; Long lines in *compilation* buffer
Date: Thu, 20 Oct 2022 11:05:41 +0200 [thread overview]
Message-ID: <m2sfji50gq.fsf@Mini.fritz.box> (raw)
In GNU Emacs 29.0.50 (build 1, aarch64-apple-darwin21.6.0, NS
appkit-2113.60 Version 12.6 (Build 21G115)) of 2022-09-21 built on
Mini.fritz.box
Repository revision: 1231a601ebe1fd9fe454c504dbeb9267440242e7
Repository branch: master
Windowing system distributor 'Apple', version 10.3.2113
System Description: macOS 12.6
Configured using:
'configure --cache-file /Users/gerd/tmp/config.cache.master
--with-native-compilation'
I did not find an easer way to reproduce this, sorry for that.
Configure Emacs with:
./configure --disable-silent-rules
so that compilation commands are shown in full.
Introduce something producing a warning or error in the C code, for
example in lisp.h.
Then do a full parallel build of Emacs (-j8 here). This produces, on my
system, lines invoking gcc which are ca. 2000 chars wide. These lines
are by default displayed with a [...].
Bug:
The errors or warnings appear sometimes truncated. For example, the file
name of the error message is not displayed. Clicking on the [...] does
not change that. (And with the truncated messages, next-error cannot
work, ...)
I have no idea what that might be, so I'm just mentioning anything that
might be relevant, such as the parallel build.
next reply other threads:[~2022-10-20 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 9:05 Gerd Möllmann [this message]
2022-11-03 6:11 ` bug#58653: 29.0.50; Long lines in *compilation* buffer Gerd Möllmann
2022-11-03 8:18 ` Eli Zaretskii
2022-11-03 8:43 ` Gerd Möllmann
2022-11-03 9:02 ` Eli Zaretskii
2022-11-03 9:10 ` Gerd Möllmann
2022-11-03 12:13 ` Gerd Möllmann
2022-11-03 12:43 ` Gerd Möllmann
2022-11-03 13:34 ` Eli Zaretskii
2022-11-03 13:39 ` Gerd Möllmann
2022-11-03 13:57 ` Gerd Möllmann
2022-11-03 14:13 ` Eli Zaretskii
2022-11-03 14:15 ` Gerd Möllmann
2022-11-03 14:37 ` Eli Zaretskii
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=m2sfji50gq.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=58653@debbugs.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).