[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#33749: 26.1; input-decode-map to empty vector should preserve echo a

From: Yuri Khan
Subject: bug#33749: 26.1; input-decode-map to empty vector should preserve echo area
Date: Tue, 1 Jan 2019 23:09:23 +0700

On Wed, Dec 26, 2018 at 3:07 AM Stefan Monnier <address@hidden> wrote:

> Note also that the current patch is likely not quite right yet anyway:
> I mostly posted it for discussion.  E.g. I think where I put it
> currently, it fails to be run for single-key commands.

Alas, it fails in more than that one way.

    (define-key input-decode-map (kbd "<f5> <f5>") [])

    <f5> (wait 1s)
    → f5-

    <f5> (again)
    → f5 f5-

i.e., although we are in the start state, the echo area contains the
last path that led to it;

    <f5> (third time)
    → f5-

    → <f5> C-g is undefined

After that it breaks:

    <f5> (and wait 1s again)
    → (nothing happens) <f5> C-g is undefined

    → <f5> x is undefined

i.e. it “heard” the <f5> but did not echo it.


    ESC (and wait 1s)
    → ESC-

    → ESC f5-


The echo area clears but the current prefix is ESC:

    → C-M-g is undefined

Do we have anything resembling a feature specification for echoing?
Automated tests? Even just a mechanism for testing key sequence
reading and echoing?

I see a file, test/src/keyboard-tests.el. I see there is a mechanism
to feed keystrokes, either immediately or on a timer. I will look if
these can be used to exercise the echoing code path.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]