From: Agustin Martin <agustin.martin@hispalinux.es>
To: 12768@debbugs.gnu.org, Reuben Thomas <rrt@sc3d.org>
Cc: agustin.martin@upm.es
Subject: bug#12768: 24.1; flyspell highlights words which ispell accepts
Date: Thu, 1 Nov 2012 01:10:11 +0100 [thread overview]
Message-ID: <CAKy3oZoenQuhKrJGeVYjKPfJnhsvKm2eynAdXK_RnE=f-k7Qmw@mail.gmail.com> (raw)
In-Reply-To: <CAOnWdogDzrfJ9=AsnNrkoUz-MdaVEA=rHfMJZnmE0F0zaP9rPA@mail.gmail.com>
2012/10/31 Reuben Thomas <rrt@sc3d.org>:
>
> On 31 October 2012 21:31, Agustin Martin <agustin.martin@hispalinux.es>
> wrote:
>>
>>
>> Can you please provide a minimal example file showing this problem?
>
>
> Attached. I visit the file, switch to autoconf-mode, and run ispell-buffer.
> Without switching to autoconf-mode, I don't get the error.
Thanks for the info,
Really strange. With your steps I can even reproduce the problem with
something as simple as
dnl -- D
If I add something before dnl I still get the problem.
sdfdsfsdnl -- D
IIf I either break the double dash (no double dashes at all) or the
dnl or remove the "D" after the dashes problem disappear
dfnl -- D
dnl - - D
dnl --
autotest-mode.el is a small file, but II do not see any hint about
what is happening here. Seems to do something strange with double
dashes associated with dnl, but I am absolutely clueless, help
welcome.
>>
>> Also, please have a look at how the spellchecking process is started
>> (relevant entry in 'ps -aux' call from a console) in case there is
>> something strange there.
>
> /usr/bin/aspell -a -m -B --encoding=utf-8
While probably unrelated, this should have a "-d en_GB" part. I am
reproducing this problem with other dicts as well as with your
british+accs entry, so this seems not the main problem.
Dirty workaround in the meantime, avoid double dashes and try something like
dnl - - - - Hi, whatever I want to add here
But I really wonder what is happening here.
--
Agustin
next prev parent reply other threads:[~2012-11-01 0:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 13:23 bug#12768: 24.1; flyspell highlights words which ispell accepts Reuben Thomas
2012-10-31 12:26 ` Agustin Martin
2012-10-31 12:31 ` Agustin Martin
2012-10-31 12:35 ` Reuben Thomas
2012-10-31 14:53 ` Agustin Martin
2012-10-31 15:20 ` Reuben Thomas
2012-10-31 20:17 ` Reuben Thomas
2012-10-31 21:31 ` Agustin Martin
2012-10-31 21:50 ` Reuben Thomas
2012-11-01 0:10 ` Agustin Martin [this message]
2012-11-01 0:55 ` Reuben Thomas
2012-11-01 14:44 ` Eli Zaretskii
2012-11-02 1:19 ` Agustin Martin
[not found] ` <24814310.2560.1351781107917.JavaMail.root@mx1-new.spamfiltro.es>
2012-11-06 17:48 ` Agustin Martin
2012-10-31 16:01 ` Glenn Morris
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='CAKy3oZoenQuhKrJGeVYjKPfJnhsvKm2eynAdXK_RnE=f-k7Qmw@mail.gmail.com' \
--to=agustin.martin@hispalinux.es \
--cc=12768@debbugs.gnu.org \
--cc=agustin.martin@upm.es \
--cc=rrt@sc3d.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 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).