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?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Newsgroups: gmane.emacs.bugs Subject: bug#58839: [Patch] Re: bug#58839: 29.0.50; project-kill-buffer fails when Eglot is running Date: Tue, 1 Nov 2022 11:36:02 +0000 Message-ID: References: <87sfj8umwb.fsf@posteo.net> <87edur3lil.fsf@posteo.net> <87a65f3j40.fsf@posteo.net> <213f3549-de4e-25a7-5e27-d13893e557bc@yandex.ru> <87zgdfwkle.fsf@gmail.com> <8e31a89d-e35e-6dd0-a8e3-f0b9684c8bfa@yandex.ru> <87v8o3wgq1.fsf@gmail.com> <87ilk2x1si.fsf@gmail.com> <871qqq7l9p.fsf@posteo.net> <87eduqwekz.fsf@gmail.com> <87wn8invbx.fsf@posteo.net> <877d0iw8iq.fsf@gmail.com> <837d0hhlke.fsf@gnu.org> <46ff0065-5645-ef1e-2621-242fb6a73f98@yandex.ru> <87v8o0uxn5.fsf@gmail.com> <787a4362-7ff5-7dbb-9118-16e4bee5f328@yandex.ru> <87edunvhf2.fsf@gmail.com> <6d4d9e72-1bae-4d64-b7c1-c2b9c11e396f@yandex.ru> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000073b88c05ec671d8e" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33449"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, Eli Zaretskii , manuel.uberti@inventati.org, 58839@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 01 12:36:30 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 1oppZF-0008RT-Uj for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 01 Nov 2022 12:36:30 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oppYy-0005cV-PN; Tue, 01 Nov 2022 07:36:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oppYp-0005XF-1Y for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2022 07:36:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oppYo-0000V6-MB for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2022 07:36:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oppYo-0007Eu-80 for bug-gnu-emacs@gnu.org; Tue, 01 Nov 2022 07:36:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?Jo=C3=A3o_?= =?UTF-8?Q?T=C3=A1vora?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 01 Nov 2022 11:36:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58839 X-GNU-PR-Package: emacs Original-Received: via spool by 58839-submit@debbugs.gnu.org id=B58839.166730251227747 (code B ref 58839); Tue, 01 Nov 2022 11:36:02 +0000 Original-Received: (at 58839) by debbugs.gnu.org; 1 Nov 2022 11:35:12 +0000 Original-Received: from localhost ([127.0.0.1]:42866 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oppXz-0007DT-Ar for submit@debbugs.gnu.org; Tue, 01 Nov 2022 07:35:11 -0400 Original-Received: from mail-oa1-f51.google.com ([209.85.160.51]:39620) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oppXx-0007D8-3R for 58839@debbugs.gnu.org; Tue, 01 Nov 2022 07:35:10 -0400 Original-Received: by mail-oa1-f51.google.com with SMTP id 586e51a60fabf-13c569e5ff5so16063927fac.6 for <58839@debbugs.gnu.org>; Tue, 01 Nov 2022 04:35:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ySz54CLs/75+7kqT7Vdy0f4+HMq5N3vdhin5y98k0sw=; b=aBaZWynci95xK6wzq/dsn0sBTtOHfsfR8+ByFrHS0M9W/MKHPdMHftyct5f3BGKTqM dd4InUo4TtOw3NmF6HyLoagw7XDw2NgKYXfV3eN09briJz+wFAeyJMsi5/KglOA88V9I AdPHeEHIMF5I2DDvyVoZ6QnFyx6e3h5cUx2UlDm1qfMALlnwPP6u0Ms/ZjHT420v5sQs r32o2OwOyJs3GuhzNNyFBBE/iIpKKxFgKLIynn3Vu+qaanIyzm1BsnAZdX6v0KgCmf1E 2ek3wXtWx/xBCZeK14Ek9BkZ53FS/L+csP4jfmAOzioexGQqQF9V1XVkI8gOlmcyp072 /+SQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ySz54CLs/75+7kqT7Vdy0f4+HMq5N3vdhin5y98k0sw=; b=WzExmbK9SAxnoOhsCmAIgvVjseDh9A/ANEU7ZKKTlfYkviiP+b6cO2giPDLhfB5A1t ZH+wBLgOLYzKeNp8hvAUqQItd6/aF4z8lhwHK/0VGCsm09CVglghDNpMzEKW50sBRhJH x9B7v2giPnspPV9h6ASushx+hlcXGxKoCyt8M16PNPZwe+0GEA7Nwhqfm4oVcCLAtoqt BuYp8uMbQMQ0q8G2oeuQRrJXdVLNnB0t16q9iqIQFmfWIQbB0iJ8W5KVfmXKf2RsCVK8 HOdIlyG8jtOOlYPLIO8TUczz++kuUUPXWphwyw1kp8Q4itlHRF90g519cLdiil0ykpfe lgng== X-Gm-Message-State: ACrzQf2hsQTLDW0QY5dmAklpYO6ZcQYgGhhQd+wFQ/pUqaUYxmeaykCn Uzgn0sx9gav17+g/GOcBxpN0MRVPjN5LKXFinR0= X-Google-Smtp-Source: AMsMyM7uL4L0WNBNya/dP+QD/PJDfAcZVaU570ONXmfKqEgCZgEGlg2APwbAr8LGW3bO++6hQbBD/4Yo90eQSy/4YDU= X-Received: by 2002:a05:6870:e242:b0:13b:d561:ad02 with SMTP id d2-20020a056870e24200b0013bd561ad02mr10936686oac.215.1667302503461; Tue, 01 Nov 2022 04:35:03 -0700 (PDT) In-Reply-To: <6d4d9e72-1bae-4d64-b7c1-c2b9c11e396f@yandex.ru> 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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:246767 Archived-At: --00000000000073b88c05ec671d8e Content-Type: text/plain; charset="UTF-8" On Mon, Oct 31, 2022 at 10:51 PM Dmitry Gutov wrote: > I suggest you try it first. It works in my test > Disaster, really? The reason I came about the Gnus problem was when using it to reply to some emails here and trying out the C-x p k and finding out all my Gnus buffers were gone. > Do you know whether CIDER will be satisfied by the same patch I sent > previously? No. I don't use it. You should ask Manuel, who reported this in the original discussion. > >>> you're making a gun that only backfires 5% of the time. > >> Yours is the first instance so far. > > We seem to use different algebraic systems. > This is literally the first bug report on the subject. It's Philip's bug report. I don't use C-x p k, in fact I learned about it here. It's then I started trying it, because in principle it is very useful, that I found out how broken it is for many other situations: ibuffer, *gnus*, and it's a shame we can't use it. > what you are doing is pressuring all other participants into your POV by > means of an insult. That usually works better if the offending code was > written by somebody who already left (the project/the discussion/the > company/etc), or is a little younger. You are attributing ill-intent to me from a moral high-ground you can't really claim. I had no idea as to the authorship, so I can't have been engaging in those perfidious tactics. But do I apologize for the word "abomination". If it helps I'll show you round to plenty such things written by myself in the past. I've explained to Philip objective reasons why I think evaluated mini-languages are almost always inferior to a decent Lisp such as Elisp. You could perfectly reasonably deprecate these two variables. > They can, though, even if odds are low. It can also happen through some > other automation, which Emacs lets the users do freely. That automation is just as buggy as C-x p k, and should be fixed, but the only such automation we know is C-x p k. > I'm fairly sure that the solution I offered would be easy enough > implement, to actually protect the vulnerable buffer. > I suppose we are not doing that, however. You sketched an untested code-less idea and I explained how flawed it was. Not to mention it's just [insert acceptably derogatory word here] to protect implementation details from misbehaving code that is under our control and can just be fixed. --00000000000073b88c05ec671d8e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Oct 31, 2022 at 10:51 PM Dmitry Gutov <dgutov@yandex.ru> wrote:

> I = suggest you try it first.

It works in my test

> Disaster, = really?

The reason I came about the Gnus problem was when using it
to reply to some emails here and trying out the C-x p k and finding = out
all my Gnus buffers were gone.=C2=A0

=
> Do you know whether CIDER will be satisfied by the same patch I = sent
> previously?

No.=C2=A0 I don't use it. You shou= ld ask Manuel, who reported this in
the original discussion.=
=C2=A0
> >>> you're making a gun that only bac= kfires 5% of the time.
> >> Yours is the first instance so far.=
> > We seem to use different algebraic systems.
> This is l= iterally the first bug report on the subject.

= It's Philip's bug report.=C2=A0 I don't use C-x p k, in fact I = learned about it
here.=C2=A0 It's then I started trying it, because = in principle it is very useful,
that I found out how broken it is f= or many other situations: ibuffer, *gnus*,
and it's a sh= ame we can't use it.
=C2=A0
> what you are doing is pressuri= ng all other participants into your POV by
> means of an insult. That= usually works better if the offending code was
> written by somebody= who already left (the project/the discussion/the
> company/etc), or = is a little younger.

You are attributing ill-intent to me from = a moral high-ground you can't really
claim.=C2=A0 I had = no idea as to the authorship, so I can't have been engaging in those
perfidious tactics.=C2=A0 But do I apologize for the word &quo= t;abomination". If it helps
I'll show you round to plent= y such things written by myself in the past.

I= 've explained to Philip objective reasons why I think evaluated
mini-languages are almost always inferior to a decent Lisp such as Elisp= .
You could perfectly reasonably deprecate these two variables.

> They can, though, even if odds are low. It can also happen= through some
> other automation, which Emacs lets the users do freel= y.

That automation is just as buggy as C-x p k, and should be fixed,= but
the only such automation we know is C-x p k.

> I'm fa= irly sure that the solution I offered would be easy enough
> impleme= nt, to actually protect the vulnerable buffer.
> I suppose we are not= doing that, however.

You sketched an untested code-less idea a= nd I explained how flawed it was.
Not to mention it's ju= st [insert acceptably derogatory word here] to protect
implementa= tion details from misbehaving code that is under our control
and can just be fixed.
--00000000000073b88c05ec671d8e--