unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Caleb Wakeman <cdw1992@twcny.rr.com>
To: 16190@debbugs.gnu.org
Subject: bug#16190: 23.4; M-x captialize-word works incorrectly
Date: Mon, 23 Dec 2013 00:35:41 -0500	[thread overview]
Message-ID: <52B7CBAD.8080605@twcny.rr.com> (raw)
In-Reply-To: <52B7BA11.10004@twcny.rr.com>

It occurred to me that there may be two separate "bugs", and me 
conflating them.

First is "M-x capitalize-word has an incorrect docstring".  That's been 
fixed (or I should say, I take your word for it).

Second is "M-x capitalize-word does the wrong thing".  Whether that's a 
bug may be open to debate (I think it is a bug, or at least a problem, 
obviously), but that hasn't changed.

On 12/22/2013 11:20 PM, Caleb Wakeman wrote:
> (paraphrased quotes)
>  >>> That's the intended behavior
>  >> Then its docstring is incorrect
>  > Fair enough, fixed
>
> Erm, well...
>
> I've had several days to think it over, and I don't agree [that it's
> fixed].  Yes, the docstring is (was) incorrect; and if it hadn't been
> incorrect, I wouldn't have reported it as a bug.
>
> However, the function would still be doing 'The Wrong Thing' (for me, I
> can imagine that cases exist where this isn't), and if I ever used it
> again, it would only be because I forgot that it didn't do what I expected.
>
> I think this is also the point where if I want something more done, I
> really should do it myself.  I'd take it on for sure if it were in
> elisp.  I dunno if I could do it in C.
>
> This seems reasonable as a 'workaround' fix, though.
>
> [I'd agree that "Severity: minor" is correct.]
>
> (I can re-create my mental state leading up to actually sending the bug
> report, or share my mental image of what the function does, if either of
> those would be helpful.)





  reply	other threads:[~2013-12-23  5:35 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
2013-12-19 17:54     ` Eli Zaretskii
2013-12-23  4:20       ` Caleb Wakeman
2013-12-23  5:35         ` Caleb Wakeman [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=52B7CBAD.8080605@twcny.rr.com \
    --to=cdw1992@twcny.rr.com \
    --cc=16190@debbugs.gnu.org \
    --cc=caleb@compwizard.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).