From: Eli Zaretskii <eliz@gnu.org>
To: "Евгений Курневский" <kurnevsky@gmail.com>
Cc: larsi@gnus.org, 53391@debbugs.gnu.org
Subject: bug#53391: First keypress doesn't work when scratch buffer is killed in emacs 28, emacs daemon + emacs client is used
Date: Fri, 21 Jan 2022 13:55:11 +0200 [thread overview]
Message-ID: <83zgnpnw0w.fsf@gnu.org> (raw)
In-Reply-To: <CAOEHfogFqst9EUkWJC2HTBamSpHGvxK2sx+Kefm5ToPRcwDmLA@mail.gmail.com> (message from Евгений Курневский on Fri, 21 Jan 2022 10:01:23 +0000)
> From: Евгений Курневский <kurnevsky@gmail.com>
> Date: Fri, 21 Jan 2022 10:01:23 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>, 53391@debbugs.gnu.org
>
> Could it be some kind of a race? When originally tried with my complete config I had different results with
> and without (require 'easy-mmode) before killing scratch buffer. Probably you can try with this line as well?
I already did, and I don't see the problem.
> Also I noticed that if you press q in this case emacs just kills this opened buffer. So probably emacs is in
> some mode in this case - can I check it somehow?
Can you type C-g and show the backtrace?
next prev parent reply other threads:[~2022-01-21 11:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 13:49 bug#53391: First keypress doesn't work when scratch buffer is killed in emacs 28, emacs daemon + emacs client is used Евгений Курневский
2022-01-20 14:13 ` Lars Ingebrigtsen
2022-01-20 14:19 ` Евгений Курневский
2022-01-20 20:32 ` Eli Zaretskii
2022-01-20 20:42 ` Евгений Курневский
2022-01-21 9:12 ` Lars Ingebrigtsen
2022-01-21 9:18 ` Евгений Курневский
2022-01-21 9:25 ` Lars Ingebrigtsen
2022-01-21 9:32 ` Евгений Курневский
2022-01-21 10:01 ` Евгений Курневский
2022-01-21 11:55 ` Eli Zaretskii [this message]
2022-01-21 12:10 ` Евгений Курневский
2022-01-21 12:57 ` Eli Zaretskii
2022-01-21 13:05 ` Евгений Курневский
2022-01-21 11:46 ` Eli Zaretskii
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=83zgnpnw0w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53391@debbugs.gnu.org \
--cc=kurnevsky@gmail.com \
--cc=larsi@gnus.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.savannah.gnu.org/cgit/emacs.git
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).