From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: branch master updated (0aa0e1f -> 9b7f9e6)
Date: Mon, 24 Feb 2020 22:22:24 +0100 [thread overview]
Message-ID: <877e0bk7e7.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87v9nvg1wf.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> More accurately, I think there was no consensus around the proposed
> changes. Ricardo and I argued in favor of honoring ‘INSIDE_EMACS’ and
> disabling colors when it is set.
>
> In terms of process, I think it’s a case where we should make sure the
> people involved in the discussion can come to an agreement before going
> further (info "(guix) Commit Access").
>
> WDYT?
I believe that all points have been answered and I waited one week as
usual.
> As I wrote elsewhere, we avoid working around terminal bugs in Guix
> itself. In this case, the bugs are in an old VTE version and about to
> be fixed in Eshell, both of which are good reasons not to try to paper
> over it in Guix.
None of the changes that I pushed deal with the terminal bugs or with
the Eshell bug. This is a separate issue.
> I see reluctance to the proposed changes in
> <https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00031.html> (I
> agree with Ricardo’s concerns).
I've addressed Ricardo's points:
- M-x shell font-locking is not influenced by the colors of the programs
being executed. M-x shell supports ANSI colors and it's expected of
programs to display colors.
- PAGER=cat does not do the job as we discussed later.
I believe the changes I pushed are going in the right direction. Please
let me know if this introduced a regression.
Cheers!
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-24 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200224101817.20439.52918@vcs0.savannah.gnu.org>
2020-02-24 15:31 ` branch master updated (0aa0e1f -> 9b7f9e6) Ludovic Courtès
2020-02-24 15:40 ` Pierre Neidhardt
2020-02-24 16:36 ` zimoun
2020-02-24 20:34 ` Ludovic Courtès
2020-02-24 21:22 ` Pierre Neidhardt [this message]
2020-02-24 23:00 ` zimoun
2020-02-24 23:45 ` Jelle Licht
[not found] ` <20200224101818.9A1FC206ED@vcs0.savannah.gnu.org>
2020-02-24 15:35 ` 01/03: ui: Only display link in capable terminals Ludovic Courtès
2020-02-24 16:15 ` Pierre Neidhardt
2020-02-24 20:38 ` Ludovic Courtès
2020-02-24 21:23 ` Pierre Neidhardt
2020-02-27 23:16 ` Ludovic Courtès
2020-02-28 7:10 ` Pierre Neidhardt
2020-02-28 14:29 ` zimoun
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e0bk7e7.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.