From: Hugh Wolf <hwolf@deutsches.lieder.de>
Subject: Re: emacs for Mac OS 10.3.1
Date: Wed, 19 Nov 2003 21:03:26 GMT [thread overview]
Message-ID: <slrnbrnmku.6u8.hwolf@esb.dsl.bbn.com> (raw)
In-Reply-To: KeQub.7405$b64.4194@okepread02
On 2003-11-19, Chris Swoyer <fswoyer@cox.net> wrote:
> I've looked at enhanced carbon emacs, but it doesn't work with
> panther yet.
I'm using it in Panther to compose this followup. It works fine for
me.
> There is another version, via fink, emacs21-xaw3d
> (also tried emacs32-nox), but I can't get my mac to build them; it
> grinds for a long time and prints a lot of stuff to screen, but
> always ends with "fatalerror 10". I then tried to install the
> binary version but get a message about unmet dependencies
> involving ncurses.
You can build an emacs 21.2 with X11 support via fink if you get the
current package descriptions (in this case emacs21 21.2-26).
There's no fink package description yet for emacs 21.3 w/X11 in the
'stable' tree. The emacs21-xaw3d you mention above is 21.3, but it's
in the 'unstable' tree, which I've found it best to avoid even though
it is more current.
> While I'm asking, what are the pluses and minuses of carbon
> emacs and emacs21-xaw3d.
You can run the X11 client remotely...
next prev parent reply other threads:[~2003-11-19 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 20:18 emacs for Mac OS 10.3.1 Chris Swoyer
2003-11-19 21:03 ` Hugh Wolf [this message]
2003-11-19 21:48 ` Tim McNamara
2003-11-20 12:51 ` Hugh Wolf
2003-11-21 17:52 ` Stephen H. Westin
2003-11-21 18:29 ` Hugh Wolf
2003-11-21 18:58 ` Stephen H. Westin
2003-11-21 19:25 ` Kevin Rodgers
2003-11-21 19:34 ` Tim McNamara
2003-11-21 18:33 ` Tim McNamara
2003-11-21 21:02 ` Hugh Wolf
2003-11-20 2:40 ` leo
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=slrnbrnmku.6u8.hwolf@esb.dsl.bbn.com \
--to=hwolf@deutsches.lieder.de \
/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).