unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 55027@debbugs.gnu.org, hmelman@gmail.com
Subject: bug#55027: 28.1; User option python-forward-sexp-function in wrong group
Date: Thu, 21 Apr 2022 21:53:07 +0300	[thread overview]
Message-ID: <83czhaqne4.fsf@gnu.org> (raw)
In-Reply-To: <87h76mgvgh.fsf@gmail.com> (message from Kévin Le Gouguec on Thu, 21 Apr 2022 20:09:02 +0200)

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Howard Melman <hmelman@gmail.com>,  55027@debbugs.gnu.org
> Date: Thu, 21 Apr 2022 20:09:02 +0200
> 
> 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 raise a brow about something in Emacs almost every day.  That
doesn't mean all those things are problems.  Let's not make a mountain
out of a molehill.

Also, let's not behave as if another opinion that's against mine will
change anything in a decision I made after careful consideration of
the possible alternatives.  Contrary to popular belief, I don't make
such decisions easily, and would appreciate some minimal credit here.

> 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.

I'm not convinced, because I considered these effects before I decided
to make that change.





      reply	other threads:[~2022-04-21 18:53 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
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 [this message]

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=83czhaqne4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=55027@debbugs.gnu.org \
    --cc=hmelman@gmail.com \
    --cc=kevin.legouguec@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).