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#56135: 29.0.50; python.el - forward-sexp regression over triple-quoted strings Date: Wed, 22 Jun 2022 23:19:40 +0100 Message-ID: References: <875yktgpiz.fsf@gmail.com> <877d58juup.fsf@gmail.com> <87y1xotlna.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000dbf59405e210b7f3" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18168"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Monnier To: =?UTF-8?Q?K=C3=A9vin?= Le Gouguec , 56135@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 23 00:19:19 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 1o48gw-0004dD-Vl for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 23 Jun 2022 00:19:19 +0200 Original-Received: from localhost ([::1]:52306 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o48gv-0001ty-UT for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 22 Jun 2022 18:19:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36654) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o48gg-0001tb-Rz for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 18:19:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42902) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o48gf-00012q-OM for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 18:19:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o48gf-0002Mc-Iz for bug-gnu-emacs@gnu.org; Wed, 22 Jun 2022 18:19:01 -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: Wed, 22 Jun 2022 22:19:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56135 X-GNU-PR-Package: emacs Original-Received: via spool by 56135-submit@debbugs.gnu.org id=B56135.16559363409077 (code B ref 56135); Wed, 22 Jun 2022 22:19:01 +0000 Original-Received: (at 56135) by debbugs.gnu.org; 22 Jun 2022 22:19:00 +0000 Original-Received: from localhost ([127.0.0.1]:36799 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o48ga-0002MJ-Oh for submit@debbugs.gnu.org; Wed, 22 Jun 2022 18:18:59 -0400 Original-Received: from mail-ot1-f44.google.com ([209.85.210.44]:38413) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o48gL-0002Ls-9B for 56135@debbugs.gnu.org; Wed, 22 Jun 2022 18:18:55 -0400 Original-Received: by mail-ot1-f44.google.com with SMTP id c3-20020a9d6843000000b0060c2c63c337so14108920oto.5 for <56135@debbugs.gnu.org>; Wed, 22 Jun 2022 15:18:41 -0700 (PDT) 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=wSAaXgrS88VWgRKdUnfqQYzasnYdcRC1oQrVgm03Wu4=; b=ldu7oIGVi+bUfb7gD2vlJP/ghafTQYhCUHfRgHWi5DTyfexV36eG3wSkq6EEwjjZOH YFmMbqH2x86ak5OD+fJJUSw49LUXNoMGp/bZc3lL3PpTGE391poh5Yo9t47tYzWxDQIE gNYR9qOdsXbEWDcR80WV5KCqJaoBlbl/h01VXf5XtXDr4RBR1fdRKn00fjDx/dqDDyfy X3cCL64K2+A+P350FGW1AGrJY65p3j1kxVvkTZwQLRjjHiBvyHGCKhLMVwqH+jTKI4Gw o9upbhKomtSk65KM8wzVVz28ZN7xJNwuh0eeZ7R4olyq7MLhK3L+ZX1VUfL1/PbEXlId qFpg== 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=wSAaXgrS88VWgRKdUnfqQYzasnYdcRC1oQrVgm03Wu4=; b=CeTN4OohedMaOrwS26WTI2ZGJW5JblpNJX+XMR2FweWd4FuULMQSCPe+CLTsQrjgHH PtpWX9CLaB4BTQrBBz+qPVyEl09m9NNCr1K2jcJrsrqLKnjkhCW4OZDJ7DB8tVjFp3Qg 7NLbqG+FUOtUpurAMxZUHbEA/EuzoNpgx8q2iIaf98v1CBXHgBfSSxlBCO2PgoTqNNYF ZqcBISuKCoucfzeZwIBnXuffk1iPNTSyJTbiguRFNsvCw8N7MOxoL5AoYSzNlM/VAWmv UJ7ZEaHDJQbsXIr68jaMaOZ4UyBwDhFu4NrAta3BYnK92nTkUivM0b+pl+xhEP8ECt8b ijOA== X-Gm-Message-State: AJIora9+hFsGCYA9alGWAxcC5F9BQ2Ca82WwbngiNw1ZCMyj1PvI5ooC U9OCYlNqPhK/x7N45incAR60K0UivZ66VZkCtcs= X-Google-Smtp-Source: AGRyM1tU2bbJMt16kLc/YxkplYmmomb+1Goqqz/D2OhQVPfXfPU+qIctd0MH3SObvnwsaIR0HnKOTZDwlQ4qWkYDI0k= X-Received: by 2002:a05:6830:18d1:b0:60b:f82f:c2f6 with SMTP id v17-20020a05683018d100b0060bf82fc2f6mr2386428ote.317.1655936315551; Wed, 22 Jun 2022 15:18:35 -0700 (PDT) In-Reply-To: <87y1xotlna.fsf@gmail.com> 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:235054 Archived-At: --000000000000dbf59405e210b7f3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Jun 22, 2022 at 10:48 PM K=C3=A9vin Le Gouguec wrote: > K=C3=A9vin Le Gouguec writes: > > > Jo=C3=A3o T=C3=A1vora writes: > > > >> On a very superficial analysis, I would say you're _not_ experiencing = a > >> bug, because setting the f-sexp-f to nil buffer-locally would mean > >> you don't want any python-specific behaviour for triple quotes. > >> > >> It might be a regression for a previous state of the working tree, but > then > >> again that state seems to have been buggy itself, undoubtedly, at leas= t > as > >> described by myself in 0646c6817139. > >> > >> Why are you setting python-forward-sexp-function to nil? > > > > [wall of text follows] > > ( > Hadn't realized we had taken this off-list. FWIW if you found all > my verbiage informative, don't hesitate to (tell me to) forward it > back on the bug tracker. > ) > Ups. That was my mistake. Wondering what to do now. Should we re-send to the tracker. Or let future generations wonder about the missing great wall of text. Anyway, I did find your wall of text informative, particularly this point. > Wondering what the best way forward would be. Maybe a third suggested > value for python-forward-sexp-function, which would handle triple-quotes > but not add those "implicit paired delimiters"? Yes, I think this makes sense. Let's see what other think, but a patch that extracts only that bit from the current functionality and puts it in a third value would be a good idea, I think. Jo=C3=A3o --000000000000dbf59405e210b7f3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Wed, Jun 22, 2022 at 10:48 PM K=C3=A9vin Le Gouguec <kevin.legouguec@gmail.com> wro= te:
K=C3=A9vin L= e Gouguec <kevin.legouguec@gmail.com> writes:

> Jo=C3=A3o T=C3=A1vora <joaotavora@gmail.com> writes:
>
>> On a very superficial analysis, I would say you're _not_ exper= iencing a
>> bug, because setting the f-sexp-f to nil buffer-locally would mean=
>> you don't want any python-specific behaviour for triple quotes= .=C2=A0
>>
>> It might be a regression for a previous state of the working tree,= but then
>> again that state seems to have been buggy itself, undoubtedly, at = least as
>> described by myself in 0646c6817139.=C2=A0
>>
>> Why are you setting python-forward-sexp-function to nil?
>
> [wall of text follows]

(
=C2=A0 =C2=A0 Hadn't realized we had taken this off-list.=C2=A0 FWIW if= you found all
=C2=A0 =C2=A0 my verbiage informative, don't hesitate to (tell me to) f= orward it
=C2=A0 =C2=A0 back on the bug tracker.
)

Ups.=C2=A0 That was my mistake.=C2= =A0 Wondering what to do now.=C2=A0 Should we re-send to the
tracker.=C2=A0 Or let future generations wonder about the missing great wa= ll of text.

A= nyway, I did find your wall of text informative, particularly this point.

> Wondering what the best way for= ward would be.=C2=A0 Maybe a third suggested
> value for python-forwa= rd-sexp-function, which would handle triple-quotes
> but not add thos= e "implicit paired delimiters"?

Yes, I t= hink this makes sense.=C2=A0 Let's see what other think, but a patch
that extracts only that bit from the current functionality and puts= it in
a third value would be a good idea, I think.

Jo=C3=A3o
--000000000000dbf59405e210b7f3--