From: Ashton Kemerling <ashtonkemerling@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: [PATCH] Fix misspelling in flyspell.el
Date: Fri, 06 Nov 2015 16:29:31 -0600 [thread overview]
Message-ID: <hb68tp611eu5h0.fsf@gmail.com> (raw)
In-Reply-To: <20151106214630.GB1829@acm.fritz.box> (Alan Mackenzie's message of "Fri, 6 Nov 2015 21:46:30 +0000")
Alan Mackenzie <acm@muc.de> writes:
> Hello, Keshav
>
> On Fri, Nov 06, 2015 at 03:16:23PM -0600, Keshav Kini wrote:
>> * flyspell.el (flyspell-goto-next-error): fix misspelling
>
>> Copyright-paperwork-exempt: yes
>> ---
>> lisp/textmodes/flyspell.el | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>> diff --git a/lisp/textmodes/flyspell.el b/lisp/textmodes/flyspell.el
>> index 6c4a731..fa3fba6 100644
>> --- a/lisp/textmodes/flyspell.el
>> +++ b/lisp/textmodes/flyspell.el
>> @@ -1673,7 +1673,7 @@ FLYSPELL-BUFFER."
>> (setq flyspell-old-buffer-error (current-buffer))
>> (goto-char pos)
>> (if (= pos max)
>> - (message "No more miss-spelled word!"))))
>> + (message "No more misspelled words!"))))
>
>> ;;*---------------------------------------------------------------------*/
>> ;;* flyspell-overlay-p ... */
>> --
>> 2.6.2
>
> I think there's a good chance that that missssspelling is deliberate, a
> little joke, something to irritate people slightly with. It would be a
> shame to correct it.
If anything, it should be left as a testament to why flyspell is
necessary.
--
Ashton
next prev parent reply other threads:[~2015-11-06 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 21:16 [PATCH] Fix misspelling in flyspell.el Keshav Kini
2015-11-06 21:46 ` Alan Mackenzie
2015-11-06 22:29 ` Ashton Kemerling [this message]
2015-11-07 8:41 ` Eli Zaretskii
2015-11-07 9:01 ` David Kastrup
2015-11-09 20:53 ` Keshav Kini
2015-11-09 21:52 ` Richard Stallman
2015-11-09 20:55 ` [PATCH v1] Reword message " Keshav Kini
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=hb68tp611eu5h0.fsf@gmail.com \
--to=ashtonkemerling@gmail.com \
--cc=emacs-devel@gnu.org \
/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.