unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58653@debbugs.gnu.org
Subject: bug#58653: 29.0.50; Long lines in *compilation* buffer
Date: Thu, 03 Nov 2022 13:43:26 +0100	[thread overview]
Message-ID: <m2o7tous29.fsf@Mini.fritz.box> (raw)
In-Reply-To: <m2r0ykutgd.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Thu, 03 Nov 2022 13:13:22 +0100")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> I had some fun, and it gets even a bit weirder: The missing text doesn't
> seem to be lost at all, it's just somewhere else.  Example:
>
>   :22: warning: 'sprintf' is deprecated: ...
>
> This should actually be xdisp.c:22:...
>
> The xdisp.c can be found above that warning as part of a long line
>
>   ebrew/Cellar/libidn2/2.3.4/include -isystem
>   /opt/homebrew/Cellarxdisp.cAWK=awk ./mapconv glibc/IBM857.gz '/^<.*[
>                       ^^^^^^^                   
>
> And the newline before "AWK=" is probably also somewhere else.
>
> That's a start :-/.

Exactly the same happens when building in M-x shell.  And it doesn't
happen in a Terminal window.





  reply	other threads:[~2022-11-03 12:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  9:05 bug#58653: 29.0.50; Long lines in *compilation* buffer Gerd Möllmann
2022-11-03  6:11 ` 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 [this message]
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=m2o7tous29.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=58653@debbugs.gnu.org \
    --cc=eliz@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).