From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: 18353@debbugs.gnu.org
Subject: bug#18353: 24.4.50; unicode chars in mode-line on tty
Date: Fri, 29 Aug 2014 21:15:41 +0300 [thread overview]
Message-ID: <83a96ni2lu.fsf@gnu.org> (raw)
In-Reply-To: <878um7ffte.fsf@tromey.com>
> From: Tom Tromey <tom@tromey.com>
> Cc: Tom Tromey <tom@tromey.com>, 18353@debbugs.gnu.org
> Date: Fri, 29 Aug 2014 09:58:37 -0600
>
> Eli> Pressing F10 should drop down the File menu. Then you can navigate
> Eli> them with arrow keys or C-f/C-b/C-n/C-p. To select, press RET, to
> Eli> exit without selecting, press C-g.
>
> Thanks. Terminal menus seem to work fine.
So this is probably a different problem.
> Eli> Not even as a literal "\u26C3" string? That would be strange,
> Eli> indeed. What do you get in the *scratch* buffer if you type
> Eli> "C-x 8 RET 26C3 RET"? Also, what is your terminal-coding-system?
>
> When I type that I just see a space, in xterm. Maybe there's a font
> problem.
Yes, most probably.
> terminal-coding-system returns utf-8-unix.
What happens if you say
C-x RET t iso-safe RET
? Do you then see \u26c3 instead of that character, in xterm? Does
it have the right color?
One other idea I have is to dump to termscript the commands Emacs
sends to the terminal, and then look at them.
Can someone else see this on the XFCE terminal (I don't have access to
a system with it)?
next prev parent reply other threads:[~2014-08-29 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 3:25 bug#18353: 24.4.50; unicode chars in mode-line on tty Tom Tromey
2014-08-29 6:36 ` Eli Zaretskii
2014-08-29 15:22 ` Tom Tromey
2014-08-29 15:54 ` Eli Zaretskii
2014-08-29 15:58 ` Tom Tromey
2014-08-29 18:15 ` Eli Zaretskii [this message]
2021-10-10 22:15 ` Stefan Kangas
2021-11-29 19:27 ` Lars Ingebrigtsen
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=83a96ni2lu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18353@debbugs.gnu.org \
--cc=tom@tromey.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.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.