From: Xah Lee <xahlee@gmail.com>
To: Agustin Martin <agustin.martin@hispalinux.es>
Cc: xah lee <xah@xahlee.org>, 1339@debbugs.gnu.org
Subject: bug#1339: flyspell-buffer extraneous message to messages buffer
Date: Fri, 8 Jul 2011 15:48:24 -0700 [thread overview]
Message-ID: <CAGOnjhRvA3PbmZ90qJF85Upsf2oW6xnUxQhLBGfLEEJqV3vomQ@mail.gmail.com> (raw)
In-Reply-To: <20110708081053.GA3832@agmartin.aq.upm.es>
i think it was on the mac. Carbon emacs. aspell i think. utf-8
encoding. It was a html file. Isn't this a 2 years old bug?
On Fri, Jul 8, 2011 at 1:10 AM, Agustin Martin
<agustin.martin@hispalinux.es> wrote:
> On Thu, Jul 07, 2011 at 10:28:05PM +0200, Lars Magne Ingebrigtsen wrote:
>> xah lee <xah@xahlee.org> writes:
>>
>> > flyspell-buffer will create a error/warning messages in *Messages*
>> > buffer for words that ether contains unicode, or html such as ?href?,
>> > or words containing apostrophe. Each of these shouldn't occure as
>> > error/warning messages.
>> >
>> > e.g.:
>> >
>> > -> href - 1770: word not found
>> > -> Youngbloodz - 1765: word not found
>
> (flyspell-external-point-words) first looks for a list of misspellings in
> the document and later walks through the list, running (flyspell-word) on
> each misspelling.
>
> Those messages should only appear for words listed as misspellings by
> spellchecker, but not found later in actual text, which is strange and
> signalled. Which spellchecker, document encoding and dictionary are you
> using?
>
> A minimal document showing that behavior should also be useful,
>
> Regards,
>
> --
> Agustin
>
next prev parent reply other threads:[~2011-07-08 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 18:29 bug#1339: flyspell-buffer extraneous message to messages buffer xah lee
2011-07-07 20:28 ` Lars Magne Ingebrigtsen
2011-07-08 8:10 ` Agustin Martin
2011-07-08 22:48 ` Xah Lee [this message]
2011-07-08 12:22 ` Xah Lee
2011-07-10 13:28 ` Lars Magne Ingebrigtsen
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=CAGOnjhRvA3PbmZ90qJF85Upsf2oW6xnUxQhLBGfLEEJqV3vomQ@mail.gmail.com \
--to=xahlee@gmail.com \
--cc=1339@debbugs.gnu.org \
--cc=agustin.martin@hispalinux.es \
--cc=xah@xahlee.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.