From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9_?= =?UTF-8?Q?=D0=9A=D1=83=D1=80=D0=BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9?= Newsgroups: gmane.emacs.bugs 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:05:47 +0000 Message-ID: References: <87a6fqzea4.fsf@gnus.org> <83k0eup2pw.fsf@gnu.org> <87v8ydwiyr.fsf@gnus.org> <878rv9wicd.fsf@gnus.org> <83zgnpnw0w.fsf@gnu.org> <83pmolnt51.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000b4ee0b05d61747bc" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14951"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 53391@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jan 21 15:03:04 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAuVM-0003gF-9f for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Jan 2022 15:03:04 +0100 Original-Received: from localhost ([::1]:33818 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nAuVL-00036Y-7a for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 21 Jan 2022 09:03:03 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:33166) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nAtdB-0000Vl-4h for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 08:07:05 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39447) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nAtd8-0005Rq-BI for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 08:07:04 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nAtd8-0004eZ-39 for bug-gnu-emacs@gnu.org; Fri, 21 Jan 2022 08:07:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9_?= =?UTF-8?Q?=D0=9A=D1=83=D1=80=D0=BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 21 Jan 2022 13:07:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53391 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 53391-submit@debbugs.gnu.org id=B53391.164277036817822 (code B ref 53391); Fri, 21 Jan 2022 13:07:02 +0000 Original-Received: (at 53391) by debbugs.gnu.org; 21 Jan 2022 13:06:08 +0000 Original-Received: from localhost ([127.0.0.1]:60583 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nAtcG-0004dN-6w for submit@debbugs.gnu.org; Fri, 21 Jan 2022 08:06:08 -0500 Original-Received: from mail-yb1-f175.google.com ([209.85.219.175]:45654) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nAtcC-0004cr-Qz for 53391@debbugs.gnu.org; Fri, 21 Jan 2022 08:06:06 -0500 Original-Received: by mail-yb1-f175.google.com with SMTP id h14so27336164ybe.12 for <53391@debbugs.gnu.org>; Fri, 21 Jan 2022 05:06:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gF0qNU7ekbkuzblX7jj3FFP+SjObRg8C0yJS/hNCSps=; b=p0RK568DzYT0BWi8SWwRByM/Km3Y5DXVkru7u4ESHK9RR63vjNhbDKXgFnVMZUnHzr gpaPmABgOvfDg6MhFOQXZbRDNqwlU9BhN62+Hh3PSunBlBRsR/TXegnVs0bBNnmLWf0k ZGzLc8sWlvJZkv4dQsV9ZrJqFK3yJqmaPnNQk8WqK1lmgSHPMkjxrzj4H9hAm49d+dBg Hgirif92vZInfjtQhgryl5cB8M1PypyV2aEOzhbY6tut7kEX9wCG/g9TimEhnix5o/es +lfM0IH8bIZuXYPqQPfBNX1n/fMUjitA5rPYFj5lx/KmQQ6zitE/X18P2crj7QvZLSVb pqBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gF0qNU7ekbkuzblX7jj3FFP+SjObRg8C0yJS/hNCSps=; b=WLRgH1ifTvgliSDprrucYVnKbl1ZC9Jk2lV3U9ONOKeSUnA0iL36zB5nXOSOqSzHQV 2Ap03ngj8V2LxtFfB7dpzYKuHuDZrmJaklABLM7h2D5EgS+LV0fiHOcZUT8BXaexjNH0 OVHdfTNzOGPZUOBW7fd+TytQphHmGZXOQ8jJjFhs64XEvy34IgSsmkpPhGxB3L1dnoNQ 6FX4tV1eWZnbu8Z21uX0jowbWPB4kA405deZs6GellXHuXVFwkPBWIaMy4JjWeHm2xfx vBYPOpY0xkjqagQH6Am84/zS2LEeIvNZ6cjRtoFr9LXVyWyFdMH/3AeaVNiHwBJ+MUCT jj5Q== X-Gm-Message-State: AOAM531xdmHa3RKzwOjD+inIVZK/TwOMcd0E/UaI+jPqS/jaHr1wL/0H q8Fbb6iQlZ7ydcwv6PwKdCs15y3s1pC/n8Cekdo= X-Google-Smtp-Source: ABdhPJyIfY75iNprPyUYA1kWTMgCP/HJSZ6SDXynnCWiGDhCzdpzQSDTfXTbGbAvL10wztbxZoIbQuXfP8qQg2QA6q0= X-Received: by 2002:a25:38c6:: with SMTP id f189mr5632892yba.35.1642770359183; Fri, 21 Jan 2022 05:05:59 -0800 (PST) In-Reply-To: <83pmolnt51.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:224770 Archived-At: --000000000000b4ee0b05d61747bc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > Why is it important to delete the *scratch* buffer in your case? It's not important. I just had it in my config for a long time since I didn't know how emacs works - I just didn't want to have one more empty buffer and wanted to see messages at startup. The problem was that I didn't know what exactly led to this behavior after updating to emacs 28 - it was unexpected for me that killing scratch buffer could cause this. But I'm completely fine with not killing it and have already updated my configs to avoid this problem. On Fri, Jan 21, 2022 at 12:57 PM Eli Zaretskii wrote: > > From: =D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9 =D0=9A=D1=83=D1=80=D0= =BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 > > Date: Fri, 21 Jan 2022 12:10:42 +0000 > > Cc: Lars Ingebrigtsen , 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? > --=20 =D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0=BC, =D0=9A=D1=83= =D1=80=D0=BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 =D0=95=D0=B2=D0=B3=D0=B5= =D0=BD=D0=B8=D0=B9. --000000000000b4ee0b05d61747bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Why is it important to delete the *scratch* buff= er in your case?

It's not important. I just ha= d it in my config for a long time since I didn't know how emacs works -= I just didn't want to have one more empty buffer and wanted to see mes= sages at startup. The problem was that I didn't know what exactly led t= o this behavior after updating to emacs 28 - it was unexpected for me that = killing scratch buffer could cause this. But I'm completely fine with n= ot killing it and have already updated my configs to avoid this problem.

On Fri, Jan 21, 2022 at 12:57 PM Eli Zaretskii <eliz@gnu.org> wrote:
> From: =D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8= =D0=B9 =D0=9A=D1=83=D1=80=D0=BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 <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 t= he
> > 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 manual= ly 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.=C2=A0 However, given that i= t
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.=C2=A0 I'm guessin= g 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?


--
=D0=A1 =D1=83=D0=B2=D0=B0=D0=B6=D0=B5=D0=BD=D0=B8=D0=B5=D0= =BC, =D0=9A=D1=83=D1=80=D0=BD=D0=B5=D0=B2=D1=81=D0=BA=D0=B8=D0=B9 =D0=95=D0= =B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9.
--000000000000b4ee0b05d61747bc--