From: Andy Spiegl <zsh.Andy@spiegl.de>
To: Zsh-Users List <zsh-users@zsh.org>
Subject: How can I debug lost keyboard input?
Date: Wed, 12 Sep 2018 20:42:27 +0200 [thread overview]
Message-ID: <20180912184227.yahwsdnwfddtqv3m@spiegl.de> (raw)
Hi,
my problem I tried to summarize in the subject line is:
Since the recent OS upgrade to Ubuntu 18.04 my zsh (5.4.2) behaves
strangely when typing keys together with Meta + Shift. The first time I
type e.g. Meta+Shift+f nothing happens. The second time (and all following
times) the bound function is executed and everything seems normal.
I've bound finer-forward-word to Meta+Shift+f and finer-backward-word to Meta+Shift+b
They are defined as follows:
--------
finer-forward-word() {
local WORDCHARS=$WORDCHARS_FINER
zle forward-word
}
finer-backward-word() {
local WORDCHARS=$WORDCHARS_FINER
zle backward-word
}
--------
export WORDCHARS='*?_-.[]~=/&;!%^(){}<>+:@'
export WORDCHARS_FINER='?~&!%'
zle -N finer-forward-word
zle -N finer-backward-word
bindkey "^[F" finer-forward-word
bindkey "^[B" finer-backward-word
--------
All my other keybindings work normally. Just these two are crazy.
BTW if I bind the functions to a different key the same thing happens.
Uhm, as if the function would have to be loaded/initialized on the first try?
I know I should let you know about the rest of my zsh config but it has
grown pretty large over the last decades. :-) But nothing except some
aliases has changed during the last months so the problem must have to do
with the upgrade.
Any ideas how I can debug this?
Thanks,
Andy
--
Experience is something you don't get until just after you need it.
(Olivier)
next reply other threads:[~2018-09-12 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 18:42 Andy Spiegl [this message]
2018-09-19 18:27 ` Andy Spiegl
2018-09-19 19:42 ` Jérémie Roquet
2018-09-20 9:47 ` Andy Spiegl
2018-09-20 10:10 ` Mikael Magnusson
2018-09-20 10:19 ` Andy Spiegl
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=20180912184227.yahwsdnwfddtqv3m@spiegl.de \
--to=zsh.andy@spiegl.de \
--cc=zsh-users@zsh.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 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).