From: "Sébastien Gendre" <seb@k-7.ch>
To: Michael Heerdegen via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Cc: Michael Heerdegen <michael_heerdegen@web.de>
Subject: Re: flyspell-prog-mode, flyspell-mode and different dictionary
Date: Wed, 24 Jul 2024 15:42:48 +0200 [thread overview]
Message-ID: <8734ny29ev.fsf@k-7.ch> (raw)
In-Reply-To: <87y15r0wza.fsf@web.de> (Michael Heerdegen via Users list for the's message of "Wed, 24 Jul 2024 14:56:41 +0200")
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
Ok. Thank you very much. :)
Michael Heerdegen via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> writes:
> Joel Reicher <joel.reicher@gmail.com> writes:
>
>> Sébastien Gendre <seb@k-7.ch> writes:
>>
>> > I checked for variable `flyspell-prog-mode-hook` with
>> > `describe-variable`, with no success.
>>
>> Undefined variables won't show up there, which is why I asked if you
>> checked the definition of the flyspell-prog-mode *function*.
>>
>> If you setq an undefined variable, it will define it, and if your
>> version of the mode references this (previously undefined) variable,
>> it will work as you expect.
>
> With other words: You can (add-hook 'flyspell-prog-mode-hook ...) even
> when flyspell-prog-mode-hook is void, without error. And enabling
> `flyspell-prog-mode' _will_ look at and use the binding.
>
>
> Michael.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2024-07-24 13:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:45 flyspell-prog-mode, flyspell-mode and different dictionary Sébastien Gendre
2024-07-23 11:41 ` Eli Zaretskii
2024-07-23 12:29 ` Joel Reicher
2024-07-23 12:49 ` Sébastien Gendre
2024-07-24 0:39 ` Joel Reicher
2024-07-24 12:56 ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-07-24 13:42 ` Sébastien Gendre [this message]
2024-07-23 14:56 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=8734ny29ev.fsf@k-7.ch \
--to=seb@k-7.ch \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).