From: Tim Visher <tim.visher@gmail.com>
To: emacs <help-gnu-emacs@gnu.org>
Subject: ispell and NSEmacs
Date: Sat, 23 Jan 2010 08:44:01 -0500 [thread overview]
Message-ID: <c115fd3c1001230544ke3599a7o83194e1574e7c1c8@mail.gmail.com> (raw)
Hello Everyone,
I recently switched from launching emacs at the command line to simply
launching it via Quicksilver. This seems to have fixed the main
problem I was having with Emacs which was an odd font selection and an
entirely broken kill-ring. However, one thing I noticed lately is
that ispell no longer works. I can run aspell via shell mode just
fine so it's on my path once bash gets to it. But when I run it from
any other buffer, emacs claims that it can't find the program. I have
just the name `aspell` in `ispell-program-name`. I assume this is
some sort of a path issues but I have no idea how to set Emacs' PATH,
either from within Emacs or somehow externally without bash.
I installed Emacs via the MacPorts port `emacs-app-devel` if that has
any bearing here.
Thoughts?
--
In Christ,
Timmy V.
http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail
reply other threads:[~2010-01-23 13:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c115fd3c1001230544ke3599a7o83194e1574e7c1c8@mail.gmail.com \
--to=tim.visher@gmail.com \
--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.
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).