From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: yurivkhan@gmail.com, 33749@debbugs.gnu.org
Subject: bug#33749: 26.1; input-decode-map to empty vector should preserve echo area
Date: Tue, 25 Dec 2018 21:44:34 +0200 [thread overview]
Message-ID: <835zvh8k7x.fsf@gnu.org> (raw)
In-Reply-To: <jwvbm59za4j.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 25 Dec 2018 14:35:13 -0500)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Tue, 25 Dec 2018 14:35:13 -0500
> Cc: 33749@debbugs.gnu.org
>
> I think The Right Thing to do is likely to move this code to
> read_key_sequence, more specifically, move it to the point where we
> *know* we really do have an event.
>
> IOW, I think the patch below might be a better option (where we test
> `indec.start > 0` to make sure some *decoded* event was read).
Where in that patch is the variable that I asked for, which would
trigger this special behavior?
next prev parent reply other threads:[~2018-12-25 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 20:48 bug#33749: 26.1; input-decode-map to empty vector should preserve echo area Yuri Khan
2018-12-15 6:57 ` Eli Zaretskii
2018-12-15 8:07 ` Yuri Khan
2018-12-15 9:09 ` Eli Zaretskii
2018-12-16 8:29 ` bug#33749: [PATCH] Preserve echo area contents when decoding an empty key sequence (Bug#33749) Yuri Khan
2018-12-19 18:05 ` bug#33749: 26.1; input-decode-map to empty vector should preserve echo area Stefan Monnier
2018-12-20 17:33 ` Yuri Khan
2018-12-20 18:56 ` Stefan Monnier
2018-12-21 18:36 ` Yuri Khan
2018-12-25 19:35 ` Stefan Monnier
2018-12-25 19:44 ` Eli Zaretskii [this message]
2018-12-25 20:07 ` Stefan Monnier
2018-12-26 3:32 ` Eli Zaretskii
2019-01-01 16:09 ` Yuri Khan
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=835zvh8k7x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33749@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=yurivkhan@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.