bug#55027: 28.1; User option python-forward-sexp-function in wrong group

["Kévin Le Gouguec" <kevin.legouguec@gmail.com>]

Eli Zaretskii <eliz@gnu.org> writes:

>> Since it's a new option, you're just extending the amount of time
>> for people to get confused by it.
>
> Confused in what way?  How can the fact that an option appears in an
> additional customization group confuse someone?

FWIW: we already have two users (Howard and myself) who raised an
eyebrow seeing this option in python-flymake, and took the time to write
a bug report about it.

It's not entirely unlikely that more Emacs 28 users will happen to see
this option in that group while perusing the python-flymake group, raise
an eyebrow, and write a report.  Even assuming they use 28.2, they might
not think to check that it is also present in the "python" group, and
might do as we did and assume it's a mistake.

And even if they see that the option is also in the "python" group, they
might not look further than "well that's silly, it shouldn't belong in
python-flymake, let's report this".  I wouldn't fault them for that.


I don't mind your solution and don't want to waste anyone's time with
this; I just saw your question and took the bait, since those
hypothetical scenarios I describe sound more likely to me than the one
you have in mind (IIUC: a user being {accustomed to,fine with,not
confused by} this new option being in the python-flymake group).

Please dismiss if you're not convinced.