From: Neil Brown <neilb@suse.de>
To: Nikita Danilov <nikita@clusterfs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.16.18 - spelling fix
Date: Mon, 29 May 2006 18:26:47 +1000 [thread overview]
Message-ID: <17530.45127.92580.684010@cse.unsw.edu.au> (raw)
In-Reply-To: message from Nikita Danilov on Monday May 29
On Monday May 29, nikita@clusterfs.com wrote:
> Neil Brown writes:
> > On Saturday May 27, jpiszcz@lucidpixels.com wrote:
> > > I was experimenting with Linux SW raid today and found a spelling error
> > > when reading the help menus...
> > >
> > > Patch attached, not sure if this is the right place to send it or if
> > > patches go to Andrew Morton (misc ones like this)...
> >
> > Thanks....
> > but more helpful than a spelling fix would be a chunk of elisp that I
> > could stick in my .emacs, which would automatically turn on flyspell
> > mode in Kconfig files, and inside comments in .c and .h files.
>
> (defun linux-c-mode ()
> ...
> (flyspell-prog-mode)
> ...)
>
Seems easy enough.... doesn't work for me :-(
Further exploration shows that I need font-lock mode enabled for it to
highlight speeling errors for me, and I never could get used to seeing
my C code look like a Disco.
It seems that flyspell-prog-mode absolutely requires font-lock as it
uses the font-lock tags to detect which text to spell check.
So I guess I need to tell font-lock that all the different text types
should be displayed in the same font.
Why is it never easy?
Thanks.
NeilBrown
next prev parent reply other threads:[~2006-05-29 8:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 0:19 Justin Piszcz
2006-05-28 11:53 ` Jan Engelhardt
2006-05-28 22:58 ` Neil Brown
2006-05-29 7:45 ` Nikita Danilov
2006-05-29 8:26 ` Neil Brown [this message]
2006-05-29 10:38 ` Neil Brown
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=17530.45127.92580.684010@cse.unsw.edu.au \
--to=neilb@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nikita@clusterfs.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®