all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Santana, Divan" <dsantana@fnb.co.za>
Cc: Help guix <help-guix@gnu.org>
Subject: Re: network-manager-openconnect setup
Date: Sun, 11 Aug 2019 15:24:06 -0400	[thread overview]
Message-ID: <87mugfa4jy.fsf@netris.org> (raw)
In-Reply-To: <87zhkgn60o.fsf@fnb.co.za> (Divan Santana's message of "Sat, 10 Aug 2019 20:34:04 +0000")

"Santana, Divan" <dsantana@fnb.co.za> writes:

> Bonus points for anyone who knows why when I copy and paste into Emacs I
> get these weird characters.
>
>    588:24  2 (inferior-package->manifest-entry "network-manager-ope…" …)

The weird characters above, "…", should be a "HORIZONTAL ELLIPSIS"
character "…" with unicode scalar value U+2026.  In the UTF-8 encoding,
the horizontal ellipsis is represented by three bytes with hex codes E2,
80, and A6.  The three weird characters "…" are what you get when
those three bytes are misinterpreted as Latin-1, a.k.a. ISO-8859-1
encoding.

Guile only outputs Unicode HORIZONTAL ELLIPSIS in backtraces if your
current locale has an encoding for that character.  Otherwise, it will
print three ASCII periods ("...") instead.  So, it appears that your
locale environment variables (the ones printed by the "locale" command)
are configured for a UTF-8 locale.

I guess that somewhere else in your system, something is configured to
use Latin-1 (ISO-8859-1) encoding.  It could be Emacs itself, or perhaps
your terminal emulator.

       Mark

  parent reply	other threads:[~2019-08-11 19:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-10 20:34 network-manager-openconnect setup Santana, Divan
2019-08-10 21:08 ` Jelle Licht
2019-09-09 20:01   ` network-manager-openconnect setup - [External Email] divan
2019-08-11 19:24 ` Mark H Weaver [this message]
2019-09-09 20:02   ` divan

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=87mugfa4jy.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=dsantana@fnb.co.za \
    --cc=help-guix@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.