From: Eli Zaretskii <eliz@gnu.org>
To: "Peter Münster" <pmlists@free.fr>
Cc: agustin.martin@hispalinux.es, 7781@debbugs.gnu.org
Subject: bug#7781: hunspell and latex-mode
Date: Tue, 29 Apr 2014 18:25:31 +0300 [thread overview]
Message-ID: <83d2g0ma38.fsf@gnu.org> (raw)
In-Reply-To: <878uqo439s.fsf@micropit.roche-blanche.homenet.org>
> From: Peter Münster <pmlists@free.fr>
> Cc: agustin.martin@hispalinux.es, 7781@debbugs.gnu.org
> Date: Tue, 29 Apr 2014 16:30:07 +0200
>
> On Tue, Apr 29 2014, Eli Zaretskii wrote:
>
> > (I have no idea why visiting the same file in Text mode avoids the
> > problem. The only difference is that in Text mode, ispell.el does not
> > skip the first 2 lines, but instead submits them to Hunspell.
>
> No. In latex-mode, emacs switches hunspell into TeX-mode with the "+".
It does both, evidently. Compare this part of your debug output (in
LaTeX buffer):
ispell-region: First skip: \documentclass at (pos,line,column): (1,1,0).
ispell-region: Continue spell-checking with hunspell and default dictionary...
ispell-region: string pos (41->41), eol: 45, [in-comment]: [nil], [add-comment]: [nil], [string]: [nil]
ispell-region: string pos (42->45), eol: 45, [in-comment]: [nil], [add-comment]: [nil], [string]: [^bla
]
with this (in Text buffer):
ispell-region: string pos (1->24), eol: 24, [in-comment]: [nil], [add-comment]: [nil], [string]: [^\documentclass{article}
]
ispell-region: string pos (24->24), eol: 41, [in-comment]: [nil], [add-comment]: [nil], [string]: [nil]
ispell-region: string pos (25->41), eol: 41, [in-comment]: [nil], [add-comment]: [nil], [string]: [^\begin{document}
]
ispell-region: string pos (41->41), eol: 45, [in-comment]: [nil], [add-comment]: [nil], [string]: [nil]
ispell-region: string pos (42->45), eol: 45, [in-comment]: [nil], [add-comment]: [nil], [string]: [^bla
]
ispell-region: string pos (45->45), eol: 60, [in-comment]: [nil], [add-comment]: [nil], [string]: [nil]
ispell-region: string pos (46->60), eol: 60, [in-comment]: [nil], [add-comment]: [nil], [string]: [^\end{document}
]
As you see, in the second case, the TeX directives are also sent to
Hunspell for checking, while in the first case they are not.
next prev parent reply other threads:[~2014-04-29 15:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 23:14 bug#7781: 23.2.91; ispell problem with hunspell and UTF-8 file Reuben Thomas
2011-01-07 13:14 ` Agustin Martin
2011-01-07 14:30 ` Reuben Thomas
2011-02-11 17:00 ` Agustin Martin
2014-10-16 13:37 ` Agustin Martin
2014-10-16 13:54 ` Eli Zaretskii
2014-10-16 14:08 ` Agustin Martin
2012-01-01 21:42 ` bug#7781: ispell problem with hunspell and UTF-8 file (and other, related hunspell problems) Richard Wordingham
2013-04-13 19:12 ` bug#7781: [PATCH] Fix ispell problem with hunspell and UTF-8 file Николай Сущенко
2013-04-14 5:42 ` Eli Zaretskii
2013-04-14 6:33 ` Николай Сущенко
2013-04-14 7:08 ` Eli Zaretskii
2013-04-20 18:43 ` Николай Сущенко
2014-04-27 21:30 ` bug#7781: hunspell and latex-mode Peter Münster
2014-04-28 15:37 ` Eli Zaretskii
2014-04-28 16:18 ` Peter Münster
2014-04-28 16:48 ` Eli Zaretskii
2014-04-28 17:17 ` Peter Münster
2014-04-28 17:32 ` Eli Zaretskii
2014-04-28 18:27 ` Peter Münster
2014-04-29 10:03 ` Agustin Martin
2014-04-29 10:13 ` Peter Münster
2014-04-29 10:21 ` Agustin Martin
2014-04-29 10:20 ` Peter Münster
2014-04-29 10:39 ` Agustin Martin
2014-04-29 11:54 ` Peter Münster
2014-04-29 12:48 ` Peter Münster
2014-04-29 13:57 ` Eli Zaretskii
2014-04-29 14:30 ` Peter Münster
2014-04-29 15:25 ` Eli Zaretskii [this message]
2014-04-29 16:34 ` Peter Münster
2014-09-25 9:54 ` bug#7781: Bug still present in hunspell 1.3.3; Eli's patch still works Reuben Thomas
2020-08-28 12:00 ` bug#7781: 23.2.91; ispell problem with hunspell and UTF-8 file Stefan Kangas
2020-08-28 12:36 ` Eli Zaretskii
2020-08-28 12:56 ` Stefan Kangas
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=83d2g0ma38.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7781@debbugs.gnu.org \
--cc=agustin.martin@hispalinux.es \
--cc=pmlists@free.fr \
/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.