all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Calvin Heim <frofroggy@gmail.com>
To: 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: Sat, 04 Jan 2020 22:48:11 -0800	[thread overview]
Message-ID: <1578206891.2605.33.camel@gmail.com> (raw)

Hi Guix developers,

When using mate-terminal version 1.12.1 (the default graphical terminal provided in Trisquel 8), Guix commands
that print hyperlinks to the terminal (such as `guix describe` and `guix show`)
print a mangled \x1b]8;; OSC character. I haven't tested the mate-terminal
package provided by Guix though, so this bug may only be visible to Trisquel users
of the Guix package manager relying on their host distribution's default terminal soon
after installing Guix.

On a related note, the procedure supports-hyperlinks in module (guix ui) checks the
environment variable INSIDE_EMACS to prevent hyperlink mangling when using Emacs.
Perhaps this procedure could be edited to solve this bug.

--
Calvin

             reply	other threads:[~2020-01-05  6:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  6:48 Calvin Heim [this message]
2020-01-06 18:37 ` 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) 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1578206891.2605.33.camel@gmail.com \
    --to=frofroggy@gmail.com \
    --cc=38940@debbugs.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 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.