all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>,
	guix-devel@gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: Re: 01/03: ui: Only display link in capable terminals.
Date: Mon, 24 Feb 2020 17:15:24 +0100	[thread overview]
Message-ID: <878sksc677.fsf@ambrevar.xyz> (raw)
In-Reply-To: <8736b0m21m.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1400 bytes --]

Ludovic Courtès <ludo@gnu.org> writes:

> So people see less information on terminals that support hyperlinks,
> right?
>
> I think there should be as much information displayed whether or not the
> terminal supports hyperlinks.  Otherwise it can be confusing.
> (Especially since we can’t tell whether the terminal really supports
> hyperlinks: we don’t know whether it displays clickable links.)
>
> Thoughts?

The file/URL was not displayed in terminals that support hyperlinks.
This was also true before this commit.

The user has to guess that they are clickable.

I agree that displaying the file / URL in all cases and making the
clickable if possible would be an improvement.

>> --- a/guix/ui.scm
>> +++ b/guix/ui.scm
>> @@ -1637,7 +1637,7 @@ DURATION-RELATION with the current time."
>>      (let* ((file   (generation-file-name profile number))
>>             (link   (if (supports-hyperlinks?)
>>                         (cut file-hyperlink file <>)
>> -                       identity))
>> +                       (cut format #f (G_ "~a~%file: ~a") <> file)))
>>             (header (format #f (link (highlight (G_ "Generation ~a\t~a")))
>
> I understand it’s a matter of taste, but I’m not a fan of the extra
> line here.

You mean the "~%" in "~a~%file: ~a"?
How would you like to display it?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-02-24 16:15 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 [this message]
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=878sksc677.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.