From: Hans de Graaff <hans@degraaff.org>
Subject: Re: Stuff I stumbeled over while writing Gnus-FAQ
Date: Tue, 31 Dec 2002 09:45:57 +0100 [thread overview]
Message-ID: <87y966h8ze.fsf@graaff.xs4all.nl> (raw)
In-Reply-To: <el7zq8lx.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Tue, 31 Dec 2002 02:29:14 +0100")
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
On Tue, 31 Dec 2002, Frank Schmitt wrote:
> Is there anybody out there using aspell together with flyspell and
> ispell.el? Where does configuration compared to ispell differ? Is it
> enough to set ispell-program-name to aspell?
(setq-default ispell-program-name "aspell")
This is all I do, and flyspell works just fine with aspell.
Hans
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2002-12-31 8:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 1:29 Frank Schmitt
2002-12-31 1:34 ` Lars Magne Ingebrigtsen
2002-12-31 11:04 ` Frank Schmitt
2002-12-31 3:55 ` Henrik Enberg
2002-12-31 8:45 ` Hans de Graaff [this message]
2002-12-31 15:35 ` Kai Großjohann
2003-01-09 18:06 ` Frank Schmitt
2003-01-10 1:59 ` Simon Josefsson
2003-01-02 18:41 ` Simon Josefsson
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=87y966h8ze.fsf@graaff.xs4all.nl \
--to=hans@degraaff.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.
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 NNTP newsgroup(s).