From: Chris Beard <wcbeard10@wabash.edu>
To: emacs-orgmode@gnu.org
Subject: starting ispell process during latex export
Date: Wed, 6 Apr 2011 00:37:28 +0900 [thread overview]
Message-ID: <BANLkTi=Cxqf1e5eGVq-4Ji9u2F+tq3DHjg@mail.gmail.com> (raw)
This looks like it may be a multidisciplinary problem, but this
mailing list has provided good solutions for these things in the past,
so I figured it would be the first place to check.
I've been exporting latex documents via org-mode, but I noticed that
the editing mode (after C-c ') was LaTeX mode without the Auctex
options that I had used on a different emacs setup. So I installed
Auctex (it now edits in pdflatex mode), but since then exporting to
Latex has been *very* slow. In fact, the whole emacs freezes up, and
the minibuffer keeps giving me these "Starting new Ispell process
[default] ..." messages. I turned on debug-on-error, but I don't get a
backtrace buffer (but I'm not very experienced at debugging in emacs,
so this may not mean anything). Here's a sample from the *Messages*
buffer:
org-babel-exp processing...
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
Position saved to mark ring, go back with M-x org-mark-ring-goto.
org-babel-exp processing...
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
org-babel-exp processing...
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
Starting new Ispell process [default] ...
Enabling Flyspell mode gave an error
org-babel-exp processing...
Does anyone have advice on fixing this?
Thank you
Chris
next reply other threads:[~2011-04-05 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 15:37 Chris Beard [this message]
2011-04-05 15:55 ` starting ispell process during latex export Antoine Levitt
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=Cxqf1e5eGVq-4Ji9u2F+tq3DHjg@mail.gmail.com' \
--to=wcbeard10@wabash.edu \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).