From: "Chris Swoyer" <fswoyer@cox.net>
Subject: Re: Aspell and Emacs
Date: Wed, 28 Jan 2004 18:30:12 -0600 [thread overview]
Message-ID: <muYRb.7362$Q_4.170@okepread03> (raw)
In-Reply-To: DrXRb.276612$0P1.80114@twister.nyc.rr.com
I'm not using fink (everything I have came via i-Installer + Emacs +
TexShop. It would
be nice to solve this with just these, but if fink is a good way to do so,
I'll give it
a shot.
Many thanks,
Chris
"Bruce Ingalls" <bingalls@fit-zones.NO-SPAM.com> wrote in message
news:DrXRb.276612$0P1.80114@twister.nyc.rr.com...
> Chris Swoyer wrote:
> > I just downloaded and installed cocoAspell 1.4.1. I am using
> > enhanced carbon emacs (under Mac's OS 10.3.2).
> >
> > 1. what do I need to insert in my .emacs file so Emacs will use
> > Aspell
> ...
> Are you using Fink? I added the following contribution recently to
> <url: http://emacro.sf.net/ > for Mac users.
>
> Hmm. I bet I can change the first line to simply
> (when (file-readable-p "/sw/bin")
> as well as drop the defun declaration...
>
>
;;__________________________________________________________________________
> ;;;; Fink Paths
> (when (and (file-readable-p "/sw/bin") (file-exists-p "/sw/sbin"))
> (defvar shell-bin-path
> '("/sw/bin" "/sw/sbin")
> "The paths where fink binaries can be found")
>
> (defun fix-shell-paths nil
> (if (and (boundp 'exec-path) (listp exec-path))
> (setq exec-path (append shell-bin-path exec-path))
> (setq exec-path shell-bin-path)))
>
> (fix-shell-paths))
next prev parent reply other threads:[~2004-01-29 0:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 3:06 Aspell and Emacs Chris Swoyer
2004-01-28 21:50 ` Martin Stemplinger
2004-01-28 22:46 ` Chris Swoyer
2004-01-29 1:35 ` Tim McNamara
2004-01-28 23:18 ` Bruce Ingalls
2004-01-29 0:30 ` Chris Swoyer [this message]
2004-01-29 20:17 ` Kevin Rodgers
-- strict thread matches above, loose matches on Subject: below --
2004-12-31 9:28 aspell and emacs Neon Absentius
2004-12-31 10:31 ` Ehud Karni
2004-12-31 22:43 ` Neon Absentius
2005-01-01 10:40 ` Eli Zaretskii
2005-01-02 13:04 ` Ehud Karni
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='muYRb.7362$Q_4.170@okepread03' \
--to=fswoyer@cox.net \
/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).