zsh-workers
 help / color / mirror / code / Atom feed
* zle and unicode (run-help triggered issue)
@ 2013-08-07 19:35 Phil Pennock
  2013-08-08 19:05 ` Peter Stephenson
  0 siblings, 1 reply; 3+ messages in thread
From: Phil Pennock @ 2013-08-07 19:35 UTC (permalink / raw)
  To: zsh-workers

Being occasionally frivolous, a while ago I set up ☛ (BLACK RIGHT
POINTING INDEX) as an alias for a command I use fairly often.  Heck,
even with digraphs, it works out to be one fewer keystrokes.

Invoking the widget which calls run-help ends up corrupting the unicode
somewhat; I'm wondering if some unmetafy is missing somewhere?  This,
being ZLE, is way outside the areas of zsh I know much about.

zsh 5.0.2, "ilmenite" is a MacOS laptop, "redoubt" is ssh'd into a BSD
machine (from ilmenite) with locale set up correctly for UTF-8 to "just
work".  I'm pasting ☛ into the "zsh -f" to avoid setting up digraphs in
-f, I'm using bindkey to get the run-help onto Esc-H, and am entering ☛,
a space, and then Esc-H.

ilmenite% bindkey -e
ilmenite% run-help ☛
翐<4b82a689>翐
No manual entry for ☛
ilmenite% 

redoubt% bindkey -e
redoubt% run-help ☛^@^@<005abb18>^@
No manual entry for ☛
redoubt%

The exact text shown changes between shell invocations and sometimes if
I run a different command, but tends to latch onto one sequence, perhaps
showing inverse ^@ (NUL) four times afterwards; the off-by-four is what
leads me to suspect unmetafy issues.

Any ideas?
-Phil


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2013-08-08 21:54 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-07 19:35 zle and unicode (run-help triggered issue) Phil Pennock
2013-08-08 19:05 ` Peter Stephenson
2013-08-08 21:54   ` Phil Pennock

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).