From: Holger Sparr <sparr+usenet@mfkrs1.mw.tu-dresden.de>
Subject: Re: ispell and LaTeX
Date: Wed, 30 Jul 2003 12:51:35 +0200 [thread overview]
Message-ID: <lnel08cmo8.fsf@mfkrs1.mw.tu-dresden.de> (raw)
In-Reply-To: 3f278e5b$1@pfaff2
On Wed, 30 Jul 2003, Stefan M. Moser wrote:
> Thanks for the tipps! The additional (require 'ispell) was necessary,
> without it ispell-parser wasn't defined at all. However, now it is
> defined with value "tex", but the ispell-process still asks about the
> "labelname" in \eqref{labelname}! There seems still something to be
> missing?!?
>
> Stefan
I´m using AUCTeX and it is working as suggested (with your value of
ispell-tex-skip-alists).
Holger
--
next prev parent reply other threads:[~2003-07-30 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-30 6:15 ispell and LaTeX Stefan M. Moser
2003-07-30 8:25 ` Holger Sparr
2003-07-30 9:22 ` Stefan M. Moser
2003-07-30 10:51 ` Holger Sparr [this message]
2003-07-30 12:32 ` Stefan M. Moser
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=lnel08cmo8.fsf@mfkrs1.mw.tu-dresden.de \
--to=sparr+usenet@mfkrs1.mw.tu-dresden.de \
/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.
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).