From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: michael_heerdegen@web.de, jporterbugs@gmail.com,
stefankangas@gmail.com, 62677@debbugs.gnu.org
Subject: bug#62677: 30.0.50; Need to find a better name for flyspell-prog-mode
Date: Thu, 07 Sep 2023 10:09:31 +0300 [thread overview]
Message-ID: <831qfa1mtw.fsf@gnu.org> (raw)
In-Reply-To: <86wmx2mrrn.fsf@mail.linkov.net> (message from Juri Linkov on Thu, 07 Sep 2023 09:30:16 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eli Zaretskii <eliz@gnu.org>, michael_heerdegen@web.de,
> jporterbugs@gmail.com, 62677@debbugs.gnu.org
> Date: Thu, 07 Sep 2023 09:30:16 +0300
>
> > Here's the plan I'd propose: Add a new defvar-local
> > `flyspell-use-prog-mode' or somesuch that major modes can set. Now,
> > when a user enables `flymake-mode' in a buffer where that variable is
> > non-nil, the extra stuff done in `flyspell-prog-mode' gets done too.
> > Then decide which built-in major modes that would benefit, and set that
> > variable in them.
> >
> > Would `prog-mode' be a candidate though, or do we expect any modes
> > inheriting from it to want the regular `flyspell-mode'?
>
> Removing flyspell-prog-mode will break a lot of user configs
> that often contain such a pair:
>
> (add-hook 'text-mode-hook 'flyspell-mode)
> (add-hook 'prog-mode-hook 'flyspell-prog-mode)
There's no intent to remove flyspell-prog-mode, just to make
flyspell-mode more intelligent.
prev parent reply other threads:[~2023-09-07 7:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 13:13 bug#62677: 30.0.50; Need to find a better name for flyspell-prog-mode Michael Heerdegen
2023-04-04 23:32 ` Payas Relekar
2023-04-05 15:04 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-05 15:26 ` Eli Zaretskii
2023-04-07 2:43 ` Richard Stallman
2023-04-07 6:39 ` Eli Zaretskii
2023-04-10 2:53 ` Richard Stallman
2023-04-10 4:48 ` Eli Zaretskii
2023-04-05 15:46 ` Dmitry Gutov
2023-04-05 16:17 ` Juri Linkov
2023-04-05 17:44 ` Michael Heerdegen
2023-04-06 12:14 ` Augusto Stoffel
2023-04-05 19:04 ` Eli Zaretskii
2023-04-05 20:29 ` Jim Porter
2023-04-06 6:24 ` Eli Zaretskii
2023-04-06 17:46 ` Jim Porter
2023-09-05 20:57 ` Stefan Kangas
2023-09-06 11:19 ` Eli Zaretskii
2023-09-06 18:51 ` Stefan Kangas
2023-09-06 19:05 ` Eli Zaretskii
2023-09-24 14:08 ` bug#62677: Merge flyspell-mode with flyspell-prog-mode Stefan Kangas
2023-09-24 15:41 ` Eli Zaretskii
2023-09-24 16:29 ` Stefan Kangas
2023-09-24 16:42 ` Eli Zaretskii
2023-09-07 6:30 ` bug#62677: 30.0.50; Need to find a better name for flyspell-prog-mode Juri Linkov
2023-09-07 7:09 ` 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=831qfa1mtw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62677@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=juri@linkov.net \
--cc=michael_heerdegen@web.de \
--cc=stefankangas@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).