From: Drew Adams <drew.adams@oracle.com>
To: Stephen Berman <stephen.berman@gmx.net>, Eli Zaretskii <eliz@gnu.org>
Cc: caleb@compwizard.net, 16190@debbugs.gnu.org
Subject: bug#16190: 23.4; M-x captialize-word works incorrectly
Date: Thu, 19 Dec 2013 08:28:20 -0800 (PST) [thread overview]
Message-ID: <c67f31a9-da7d-4de7-aff7-82f8d647604f@default> (raw)
In-Reply-To: <87ppotuti1.fsf@rosalinde.fritz.box>
> > That's how capitalize-word is supposed to work. It's not a bug, but
> > intended behavior.
>
> Then its doc string is incorrect:
>
> capitalize-word is an interactive built-in function in `C source code'.
>
> It is bound to M-c.
>
> (capitalize-word ARG)
>
> Capitalize the following word (or ARG words), moving over.
> This gives the word(s) a first character in upper case
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> and the rest lower case.
> ^^^^^^^^^^^^^^^^^^^^^^^^
> With negative argument, capitalize previous words but do not move.
The key here is the *word that starts at point*. With point after the `n'
here: "another", the word that starts at point is "other".
It could help for the doc to explicitly emphasize this, as an extra tip.
That is, to point out that there is no scanning backward to find the
maximal word, i.e., to find a non word-constituent character.
But this should be treated as extra info, implied by a statement
(missing, it seems) that the word starts at point. "The following word"
is too loose a description to make this clear.
next prev parent reply other threads:[~2013-12-19 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 4:03 bug#16190: 23.4; M-x captialize-word works incorrectly Caleb Wakeman
2013-12-19 3:51 ` Eli Zaretskii
2013-12-19 8:36 ` Stephen Berman
2013-12-19 16:28 ` Drew Adams [this message]
2013-12-19 17:54 ` Eli Zaretskii
2013-12-23 4:20 ` Caleb Wakeman
2013-12-23 5:35 ` Caleb Wakeman
2013-12-23 16:12 ` Eli Zaretskii
2013-12-23 18:59 ` Josh
2013-12-27 3:30 ` Kevin Rodgers
2013-12-28 5:31 ` Josh
2013-12-28 19:31 ` Kevin Rodgers
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=c67f31a9-da7d-4de7-aff7-82f8d647604f@default \
--to=drew.adams@oracle.com \
--cc=16190@debbugs.gnu.org \
--cc=caleb@compwizard.net \
--cc=eliz@gnu.org \
--cc=stephen.berman@gmx.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.