From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: 01/03: ui: Only display link in capable terminals.
Date: Fri, 28 Feb 2020 15:29:18 +0100 [thread overview]
Message-ID: <CAJ3okZ0Ze9gTJYgg2AEfOegvQtbwJ-ydvmuoJfHoVo+pezjLQg@mail.gmail.com> (raw)
In-Reply-To: <87wo87aaeu.fsf@gnu.org>
Hi Ludo,
On Fri, 28 Feb 2020 at 00:16, Ludovic Courtès <ludo@gnu.org> wrote:
> I’ve reverted it in c2f9ea2b502a617bb69227d5f858eee9d4288a6a, also
> because if was causing a test failure.
I understand and I am fine.
This needs more discussion and polishing.
> The way I see it, it’s on purpose that this piece of information was not
> displayed before. For example, I think ‘guix describe’ should be
> to-the-point.
>
> More generally, hyperlinks were introduced as a way to enhance the user
> experience for those using capable terminals. Like for hyperlinks in
> HTML, it’s a way to convey additional information; displaying all these
> links in addition to the “invisible” hyperlink data can only lead to
> clutter IMO, and defeats the point of hyperlinks.
I do not buy your argument. :-)
Hyperlinks means 2 things: how the link is displayed and how to follow
the link. And they are generally connected. If you can click to the
link to follow it then you can display it as you want.
The point is to control how to display the link; whatever the way to follow it.
However, I agree that INSIDE_EMACS is not the right environment
variable to deal with that.
> Ludo’, who’s supposed to be mostly away from keyboard this week. :-)
Enjoy your holidays! :-)
Cheers,
simon
prev parent reply other threads:[~2020-02-28 14:29 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
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 [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ0Ze9gTJYgg2AEfOegvQtbwJ-ydvmuoJfHoVo+pezjLQg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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/guix.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).