From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Transforming paths in compilation output (containerized builds)
Date: Sun, 08 Dec 2024 21:45:15 +0200 [thread overview]
Message-ID: <1490.88000632531$1733687165@news.gmane.org> (raw)
In-Reply-To: <CAP_d_8WtjdFU52piwm3qj4YSit8LarHTwQpY+V43f3UuvqhDMQ@mail.gmail.com> (Yuri Khan's message of "Sun, 8 Dec 2024 13:32:27 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Sun, 8 Dec 2024 at 12:43, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> > > Is compilation-transform-file-match-alist what you are looking for?
>> >
>> > The variable talks only about errors. Does it apply to all messages not just
>> > the errors?
>>
>> It is applied to all messages.
>
> In my experience, it is not applied to messages as such. It is
> consulted when building text properties while fontifying the messages
> so that the user can jump to error locations; but the actual visible
> text in the buffer remains unmodified.
That the actual text remains unmodified is good, it's actually better
since it doesn't reveal any private information/makes the output depend on the
users machine.
As long as it applies to all messages it's good. Maybe the description
or the name of the variable should be changed then.
I looked at the integration for the other container engines for
inspiration on how to solve this issue.
None of them handle this issue or are affected.
next prev parent reply other threads:[~2024-12-08 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y10rnu37.fsf@>
2024-12-07 20:21 ` Transforming paths in compilation output (containerized builds) Eli Zaretskii
2024-12-07 21:17 ` Björn Bidar
[not found] ` <87plm3nqfr.fsf@>
2024-12-08 5:42 ` Eli Zaretskii
2024-12-08 6:32 ` Yuri Khan
2024-12-08 7:04 ` Eli Zaretskii
2024-12-08 19:45 ` Björn Bidar [this message]
[not found] ` <87frmy2c38.fsf@>
2024-12-08 20:44 ` Eli Zaretskii
[not found] <6754a91d.050a0220.355713.95f8SMTPIN_ADDED_BROKEN@mx.google.com>
2024-12-08 6:24 ` Yuri Khan
2024-12-07 19:58 Björn Bidar
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='1490.88000632531$1733687165@news.gmane.org' \
--to=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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.
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).