From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: vjp2.at@at.BioStrategist.dot.dot.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Ispell and emacs
Date: Mon, 12 Nov 2007 20:11:45 +0100 [thread overview]
Message-ID: <3B93DE55-2F88-4E7A-850B-E296E84B87F1@Web.DE> (raw)
In-Reply-To: <fh9a2v$gb1$1@reader1.panix.com>
Am 12.11.2007 um 11:31 schrieb vjp2.at@at.BioStrategist.dot.dot.com:
> A much more fundamental (machine independent) question: assuming
> everything is installed correctly, do I need to tell emacs where
> ispell is?
> After moving ispell.el into /lisp, do I need to edit the el file
> to do this?
Why don't you check and correct all ispell related variable values? C-
h v ispell- TAB TAB C-g and then change to *Completions* buffer
without actually starting any completion action. Best rename and save
it to prevent its destruction when doing some other completion.
There is also the info hypertext system. It will explain what one can
or must do with ispell.
--
Greetings
Pete
What’s the difference between OS X and Vista?
Microsoft employees are excited about OS X…
next prev parent reply other threads:[~2007-11-12 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 0:57 Ispell and emacs vjp2.at
2007-11-10 11:30 ` Eli Zaretskii
2007-11-12 10:17 ` vjp2.at
2007-11-12 21:11 ` Eli Zaretskii
[not found] ` <mailman.3376.1194901930.18990.help-gnu-emacs@gnu.org>
2007-11-12 22:53 ` David Kastrup
2007-11-14 3:02 ` vjp2.at
2007-11-14 3:01 ` vjp2.at
2007-11-14 4:10 ` Eli Zaretskii
2007-11-12 10:31 ` vjp2.at
2007-11-12 19:11 ` Peter Dyballa [this message]
2007-11-12 21:13 ` Eli Zaretskii
2007-11-13 3:37 ` vjp2.at
2007-11-13 4:14 ` Eli Zaretskii
2007-11-14 3:03 ` vjp2.at
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 2:57 ispell " Alexander Nikolov
2003-05-22 6:17 ` Sergei Pokrovsky
2003-05-22 12:30 ` Alexander Nikolov
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=3B93DE55-2F88-4E7A-850B-E296E84B87F1@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.org \
--cc=vjp2.at@at.BioStrategist.dot.dot.com \
/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).