unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Howard <christopher@librehacker.com>
To: Michael Rohleder <mike@rohleder.de>
Cc: 41034@debbugs.gnu.org
Subject: bug#41034: guix info: display messed up in emacs info
Date: Tue, 02 Jun 2020 05:33:30 -0800	[thread overview]
Message-ID: <6a9292386550c21f0ca442e5dcd5a2e887c62c34.camel@librehacker.com> (raw)
In-Reply-To: <87ftbeudrw.fsf@rohleder.de>

Hi, thank you, but problem is gone now. I can't quite recall, but I
think it went away after I ran fc-cache -f -v.

-- 
Christopher Howard
p: +1 (907) 374-0257
w: https://librehacker.com
social: https://gnusocial.club/librehacker
gpg: ADDEAADE5D607C8D (keys.gnupg.net)

On Tue, 2020-06-02 at 09:29 +0200, Michael Rohleder wrote:
> Hi Christopher,
> 
> Christopher Howard <christopher.howard@qlfiles.net> writes:
> > Hi, the guix info pages display fine when viewed with the normal
> > info
> > command, but when viewed with emacs (C-h i m Guix) there is strange
> > issue where text between forward and backquote symbols shows up as
> > hex
> > numbers. See section 6.2 for a representative example. I get the
> > same
> > result if I run `emacs -q'. I've attached some screenshots which
> > hopefully make it through the filters.
> 
> I can not reproduce this.
> I think there might be something wrong with your theme or fonts or
> so.
> 
> Can you please try with `emacs -Q` ?
> (-q still loads x-resources etc...)
> 





  reply	other threads:[~2020-06-02 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-02 22:14 bug#41034: guix info: display messed up in emacs info Christopher Howard
2020-06-02  7:29 ` Michael Rohleder
2020-06-02 13:33   ` Christopher Howard [this message]
2020-06-02 14:57     ` Michael Rohleder

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=6a9292386550c21f0ca442e5dcd5a2e887c62c34.camel@librehacker.com \
    --to=christopher@librehacker.com \
    --cc=41034@debbugs.gnu.org \
    --cc=mike@rohleder.de \
    /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).