unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Jack Hill <jackhill@jackhill.us>
To: "Ludovic Courtès" <ludo@gnu.org>
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: Thu, 9 Jan 2020 22:16:14 -0500 (EST)	[thread overview]
Message-ID: <alpine.DEB.2.20.2001092214040.11560@marsh.hcoop.net> (raw)
In-Reply-To: <87woa0tjbv.fsf@gnu.org>

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

Hi Ludo'

On Thu, 9 Jan 2020, Ludovic Courtès wrote:

>> 1. Instead of INSIDE_EMACS, the variable name NO_SUPPORT_HYPERLINK or
>> other seems more meaningful. Maybe?
>
> Actually the goal was to remove ‘INSIDE_EMACS’ from there once a
> widespread-enough Emacs version supports it, which could be within a
> year.  And since other terminals are supposed to ignore it altogether, I
> would rather not add a special environment variable.

Which Emacs version support it? I'm using Emacs 26.3 from master, and see 
the escape sequences in eshell. They seem to be correctly ignored in M-x 
shell.

Thanks,
Jack

  parent reply	other threads:[~2020-01-10  3:17 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
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 [this message]
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=alpine.DEB.2.20.2001092214040.11560@marsh.hcoop.net \
    --to=jackhill@jackhill.us \
    --cc=38940@debbugs.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).