Re: Strange problem with bindkey keys passing through to apps

[David Woodfall <dave@xxxxxxxxxxxxxx>]

On Friday 14 September 2018 12:45,
Daniel Shahaf <danielsh@xxxxxxxxxx> put forth the proposition:

> Re-sending from another address since your MTA bounced when I sent it
> the first time.  Please add zsh-users@ on reply if appropriate.

I managed to completely mess up my DNS. Seems OK now (hopefully).

> Daniel Shahaf wrote on Fri, 14 Sep 2018 12:43 +0000:
> > David Woodfall wrote on Fri, 14 Sep 2018 12:38 +0100:
> > > The binds work fine except when I try to use them while running an
> > > app - e.g. weechat, mutt - they fail and e.g. mutt will see it as the
> > > bind to save the mail.
> > >
> > > It seems that zsh isn't grabbing the keys for some reason and they
> > > are falling through to the apps.
> > >
> > > Any ideas why these are passing through to apps and not grabbed by the shell?
> >
> > That's how terminals work: input is sent only to the foreground process.
> > This is true not just for chorded keystrokes but for unchorded ones as
> > well: it's why when you open zsh from mutt (in this order) you can type
> > the command "mv" without composing a letter to somebody named "v".

I guess I was expecting something like in urxvt, when it grabs keys
and stops them reaching any applications. Screen does that too, even
in a plain console it grabs ctrl-a away from applications.

It's strange that it happens even when the applications don't have
binds for those keys though. I've now set one up in weechat for it,
but it will be annoying to have to do that for everything, that's if
they even do allow custom keybinds.

--

+#if defined(__alpha__) && defined(CONFIG_PCI)
+       /*
+        * The meaning of life, the universe, and everything. Plus
+        * this makes the year come out right.
+        */
+       year -= 42;
+#endif
  -- From the patch for 1.3.2: (kernel/time.c), submitted by Marcus Meissner

                                                            .--.  oo
                                                           (____)//
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'