Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Riley <rileyrg@gmail.com>
To: ding@gnus.org
Subject: Re: flyspell in gnus
Date: Tue, 21 Aug 2012 00:58:12 +0100	[thread overview]
Message-ID: <0hd32l6rqj.fsf@news.eternal-september.org> (raw)
In-Reply-To: <b4mtxvxc3il.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Richard wrote:
>> Sergio Martínez <samf0xb58 <at> gmail.com> writes:
>
>>> What's the value of `flyspell-highlight-flag' and
>>> `flyspell-highlight-properties'?
>
>> Its set to t.
>
>> HIliting works everywhere else : just not in gnus message
>> buffers. flyspell mode is on.
>
> The value of `flyspell-generic-check-word-predicate' in a
> message-mode buffer is `mail-mode-flyspell-verify', isn't it?

Yes

> This is set in a mail-mode buffer and a message-mode buffer; it
> limits flyspell so as to work on only lines that are in a body
> and don't begin with `>', `}', `|', or `To:'.  So, it won't work
> in quoted lines.  Try this to make flyspell work everywhere in
> a message-mode buffer (eval this in a message-mode buffer):
>
> (setq flyspell-generic-check-word-predicate nil)

I just did "bfore" typing this. No joy.

But it knows the word is wrong as flyspell-auto-correct-word works on
the unhilited mistake.

>
> Otherwise: flyspell uses overlay to highlight words.  If some
> hook (message-*-hook, post-command-hook, etc.) kills ovarlays
> you won't see incorrect words highlighting.
>

Hmm, No idea what could be gnus specific then . It works everywhere else
where overlays are used I think (autocomplete stuff).

Thanks for the info.




      reply	other threads:[~2012-08-20 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 21:12 Richard Riley
2012-05-09 10:16 ` Noorul Islam Kamal Malmiyoda
2012-05-09 14:02   ` Richard Riley
2012-05-09 21:43     ` Sergio Martínez
2012-08-19 13:05       ` Richard
2012-08-20  9:32         ` Katsumi Yamaoka
2012-08-20 23:58           ` Richard Riley [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0hd32l6rqj.fsf@news.eternal-september.org \
    --to=rileyrg@gmail.com \
    --cc=ding@gnus.org \
    /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 NNTP newsgroup(s).