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)...
Justin.
> I was experimenting with Linux SW raid today and found a spelling error when
> reading the help menus...
>
Just one? :) The kernel is full of them...
> Patch attached, not sure if this is the right place to send it or if patches go
> to Andrew Morton (misc ones like this)...
Jan Engelhardt
--
On Saturday May 27, [email protected] 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.
The first bit is probably trivial. The second has got to be
possible...
Or maybe just keep posting patches like this in the hope of shaming
people like me into learning how to spell....
;-)
Thanks.
NeilBrown
>
> Justin.
>
> diff -uprN linux-2.6.16.18/drivers/md/Kconfig linux-2.6.16.18-diff/drivers/md/Kconfig
> --- linux-2.6.16.18/drivers/md/Kconfig 2006-05-22 14:04:35.000000000 -0400
> +++ linux-2.6.16.18-diff/drivers/md/Kconfig 2006-05-27 20:14:50.501458687 -0400
> @@ -90,7 +90,7 @@ config MD_RAID10
> depends on BLK_DEV_MD && EXPERIMENTAL
> ---help---
> RAID-10 provides a combination of striping (RAID-0) and
> - mirroring (RAID-1) with easier configuration and more flexable
> + mirroring (RAID-1) with easier configuration and more flexible
> layout.
> Unlike RAID-0, but like RAID-1, RAID-10 requires all devices to
> be the same size (or at least, only as much as the smallest device
Neil Brown writes:
> On Saturday May 27, [email protected] 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)
...)
>
> The first bit is probably trivial. The second has got to be
> possible...
>
> Or maybe just keep posting patches like this in the hope of shaming
> people like me into learning how to spell....
>
> ;-)
>
> Thanks.
>
> NeilBrown
Nikita.
On Monday May 29, [email protected] wrote:
> Neil Brown writes:
> > On Saturday May 27, [email protected] 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
On Monday May 29, [email protected] wrote:
>
> 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?
Well, it's not that hard.
(custom-set-variables
;; custom-set-variables was added by Custom -- don't edit or cut/paste it!
;; Your init file should contain only one such instance.
'(global-font-lock-mode t nil (font-lock))
'(show-trailing-whitespace t))
(custom-set-faces
;; custom-set-faces was added by Custom -- don't edit or cut/paste it!
;; Your init file should contain only one such instance.
'(font-lock-builtin-face ((((class color) (background light)) nil)))
'(font-lock-comment-face ((((class color) (background light)) nil)))
'(font-lock-constant-face ((((class color) (background light)) nil)))
'(font-lock-function-name-face ((((class color) (background light)) nil)))
'(font-lock-keyword-face ((((class color) (background light)) nil)))
'(font-lock-string-face ((((class color) (background light)) nil)))
'(font-lock-type-face ((((class color) (background light)) nil)))
'(font-lock-variable-name-face ((((class color) (background light)) nil))))
The bold-red for trailing white space is possibly a little too much
... but maybe that is a good thing?
Maybe I'll make feewer typoes now.
NeilBrown