unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Calvin Heim <frofroggy@gmail.com>
Cc: 38940@debbugs.gnu.org
Subject: bug#38940: \x1b]8; ; OSC character displayed on hyperlinks shown after calls to `guix describe` or `guix show` on mate-terminal 1.12.1 (Trisquel 8)
Date: Wed, 08 Jan 2020 22:28:46 +0100	[thread overview]
Message-ID: <877e21eiy9.fsf@gnu.org> (raw)
In-Reply-To: <1578475589.2665.55.camel@gmail.com> (Calvin Heim's message of "Wed, 08 Jan 2020 01:26:29 -0800")

Hi,

Calvin Heim <frofroggy@gmail.com> skribis:

> On Tue, 2020-01-07 at 12:58 +0100, zimoun wrote:
>> Does the environment variable NO_OSC appears to you more meaningful
>> than INSIDE_EMACS?
>
> It is more meaningful, but this terminal does interpret other operating system codes,
> like OSC 12 for changing the cursor color. NO_OSC_8 would be specific to hyperlinks.

The theory is that terminals should ignore OSC codes that they do not
support.  Good’ol xterm, for instance, silently ignores those hyperlink
codes, whereas GNOME Terminal interprets them nicely.

So I would say that this is a bug in this version of mate-terminal, or
perhaps in the libvte version it’s using?

I’ve just tried mate-terminal 1.22.0 on vte 0.58.3 from Guix, and it
silently ignores those codes.

Thanks,
Ludo’.

  reply	other threads:[~2020-01-08 21:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  6:48 bug#38940: \x1b]8; ; OSC character displayed on hyperlinks shown after calls to `guix describe` or `guix show` on mate-terminal 1.12.1 (Trisquel 8) Calvin Heim
2020-01-06 18:37 ` zimoun
2020-01-06 20:26   ` Calvin Heim
2020-01-07 11:58     ` zimoun
2020-01-08  9:26       ` Calvin Heim
2020-01-08 21:28         ` Ludovic Courtès [this message]
2020-01-08 22:54           ` Calvin Heim
2020-01-09 12:09             ` zimoun
2020-01-09 21:24             ` Ludovic Courtès
2020-01-09 12:17           ` zimoun
2020-01-09 21:23             ` Ludovic Courtès
2020-01-09 21:31               ` zimoun
2020-01-10  3:16               ` Jack Hill
2020-01-10 13:51                 ` Ludovic Courtès

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=877e21eiy9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38940@debbugs.gnu.org \
    --cc=frofroggy@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 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).