From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: N-key rollover keyboards
Date: Tue, 4 Aug 2020 22:12:30 -0500 [thread overview]
Message-ID: <20200805031230.GA1850@scrozzle> (raw)
In-Reply-To: <tuxicohu.dag@gnui.org>
On 2020-08-04 at 20:25:17 +0300,
Dmitry Alexandrov <dag@gnui.org> wrote:
> 2QdxY4RzWzUUiLuE@potatochowder.com wrote:
> > On 2020-08-03 at 14:48:34 -0700,
> > Alan Davis <alan3davis@gmail.com> wrote:
> >
> >> Is there a similar tool that can be used in bash?
> >
> > There's xev, but the output is not nearly as concise.
>
> xev has nothing to do with Bash.
>
> > xev is in a package called xorg-apps
>
> Exactly! It creates an X window and thus is absolutely unsuitable for testing what your terminal recognizes / intercepts.
The OP mentioned i3, an X window manager, more than once, and
specifically used the phrase "terminal emulator," which usually means an
X application that emulates a terminal. I agree that xev can't test
exactly what your terminal receives, but it can tell you what the X
server saw from the keyboard, and could provide clues as to which key
combinations are or aren't getting to the applications.
next prev parent reply other threads:[~2020-08-05 3:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 10:59 issue with keyboard input for multiple keys Ctrl-b / nkey rollover? Alan Davis
2020-08-02 11:45 ` 2QdxY4RzWzUUiLuE
2020-08-02 16:55 ` Alan Davis
2020-08-02 13:50 ` Yuri Khan
2020-08-02 15:02 ` Perry Smith
2020-08-02 16:49 ` Alan Davis
2020-08-02 17:04 ` N-key rollover keyboards (was: issue with keyboard input for multiple keys Ctrl-b / nkey rollover?) Dmitry Alexandrov
2020-08-02 17:47 ` Alan Davis
2020-08-03 18:17 ` N-key rollover keyboards Dmitry Alexandrov
2020-08-03 21:48 ` Alan Davis
2020-08-03 22:11 ` 2QdxY4RzWzUUiLuE
2020-08-04 10:07 ` Alan Davis
2020-08-04 11:29 ` Yuri Khan
2020-08-04 17:46 ` Dmitry Alexandrov
2020-08-04 18:47 ` Yuri Khan
2020-08-04 17:25 ` Dmitry Alexandrov
2020-08-05 3:12 ` 2QdxY4RzWzUUiLuE [this message]
2020-08-04 17:22 ` Dmitry Alexandrov
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200805031230.GA1850@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--cc=help-gnu-emacs@gnu.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.
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).