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 14:57:30 +0200 [thread overview]
Message-ID: <83pmolnt51.fsf@gnu.org> (raw)
In-Reply-To: <CAOEHfoidyLNzBSstmAMn7D-zUfK+iP=_2v8YVQ44Nwi683X0VQ@mail.gmail.com> (message from Евгений Курневский on Fri, 21 Jan 2022 12:10:42 +0000)
> From: Евгений Курневский <kurnevsky@gmail.com>
> Date: Fri, 21 Jan 2022 12:10:42 +0000
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, 53391@debbugs.gnu.org
>
> > Does this mean you see the problem in stock Emacs 28 built from the
> > emacs-28 branch of the upstream Emacs repository on Savannah?
>
> Not exactly, it fetches https://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-28.0.91.tar.gz and builds
> it.
> But it doesn't apply any custom changes, and to build emacs manually I'd anyway have to get the same
> environment where it's built and do almost the same things - nixos is a bit more complex system than usual
> linux.
>
> > Can you type C-g and show the backtrace?
>
> Tried to do it with (toggle-debug-on-quit), but just got 'Debugger entered--Lisp error: (quit)'
I think I've succeeded in reproducing this. However, given that it
only happens if the init file deletes the *scratch* buffer (which is
the current buffer available to the daemon initially), I wonder
whether it's important to solve this corner case. I'm guessing that
this has something to do with the fact that the daemon performs some
initial processing of the client commands in the original buffer.
Why is it important to delete the *scratch* buffer in your case?
next prev parent reply other threads:[~2022-01-21 12:57 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
2022-01-21 12:10 ` Евгений Курневский
2022-01-21 12:57 ` Eli Zaretskii [this message]
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=83pmolnt51.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).