all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Ispell and emacs
Date: Mon, 12 Nov 2007 23:13:45 +0200	[thread overview]
Message-ID: <ulk93dv5i.fsf@gnu.org> (raw)
In-Reply-To: <fh9a2v$gb1$1@reader1.panix.com> (vjp2.at@at.BioStrategist.dot.dot.com)

> From: vjp2.at@at.BioStrategist.dot.dot.com
> Date: Mon, 12 Nov 2007 10:31:59 +0000 (UTC)
> 
> A much more fundamental (machine independent) question: assuming
> everything is installed correctly, do I need to tell emacs where ispell is?

Ispell should be on PATH somewhere, that's all.

> After moving ispell.el into /lisp, do I need to edit the el file
> to do this?

You don't, but I don't recommend moving ispell.el into lisp/, since
there should already be such a file there.  I suggest to use ispell.el
that came with Emacs, because you might have compatibility problems
(between ispell.el and the rest of Emacs) otherwise.

  parent reply	other threads:[~2007-11-12 21:13 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
2007-11-12 21:13   ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ulk93dv5i.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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 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.