Re: Word boundaries in wdired mode

[martin rudalics]

> This does indeed fix it.  I suggest it be installed even if it's
> somewhat suboptimal.

I still have to learn how to install patches.

Anyway, if people think that this patch is sufficient, the doc strings
and manual entries for `downcase-word', `upcase-word', `capitalize-word'
should explain that similar to `kill-word' they operate on the entire
region from `point' to the end (or beginning) of the next (or previous)
word and not on individual words alone.  These commands will fail when
there's a non-word, read-only character in that region.

BTW the `backward-word' doc-string should be corrected as well: "Move
backward until encountering the beginning of a word." is incorrect with
a negative argument (unfortunately).

I think that `downcase-word' and friends should downcase word characters
and not touch anything else.  Implementing that efficiently would
require a C level function (similar to scan_words) that skips any
non-word characters after or before `point'.