From: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55027@debbugs.gnu.org, Howard Melman <hmelman@gmail.com>
Subject: bug#55027: 28.1; User option python-forward-sexp-function in wrong group
Date: Wed, 20 Apr 2022 08:31:05 +0200 [thread overview]
Message-ID: <87pmlcxo46.fsf@gmail.com> (raw)
In-Reply-To: <83sfq8ticn.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Apr 2022 08:49:12 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Tue, 19 Apr 2022 17:27:42 -0400
>>
>> The defcustom for python-forward-sexp-function in python.el is in the
>> python-flymake defgroup. I believe it should be in the python defgroup.
>
> We could make it be in both groups, if that makes sense.
>
>> It should probably be moved to the ;;; Navigation section of the file,
>> but certainly before the defgroup for python-flymake
>
> Why does its exact position in the source file matter?
FWIW, this has been fixed on the master branch, in bug#51807. IIRC the
issue (and the reason for Howard's suggestion) is that python.el has two
`defgroup' clauses (python and python-flymake), and the new option was
declared after the latter, which makes the Custom machinery think it
belongs in the latter.
next prev parent reply other threads:[~2022-04-20 6:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 21:27 bug#55027: 28.1; User option python-forward-sexp-function in wrong group Howard Melman
2022-04-20 5:49 ` Eli Zaretskii
2022-04-20 6:31 ` Kévin Le Gouguec [this message]
2022-04-20 13:50 ` Howard Melman
2022-04-20 19:55 ` Kévin Le Gouguec
2022-04-21 6:07 ` Eli Zaretskii
2022-04-21 12:06 ` Howard Melman
2022-04-21 12:44 ` Eli Zaretskii
2022-04-21 14:33 ` Howard Melman
2022-04-21 15:37 ` Eli Zaretskii
2022-04-21 15:46 ` Howard Melman
2022-04-21 18:09 ` Kévin Le Gouguec
2022-04-21 18:53 ` 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=87pmlcxo46.fsf@gmail.com \
--to=kevin.legouguec@gmail.com \
--cc=55027@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hmelman@gmail.com \
/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).