From: Hugo Wolf <hwolf@deutsches.lieder.net>
Subject: Re: installing emacs and X11 on OS X
Date: Wed, 23 Oct 2002 13:01:31 GMT [thread overview]
Message-ID: <L4xt9.68493$qM2.19402@sccrnsc02> (raw)
In-Reply-To: wzfzuxz71g.fsf@localhost.cs.uu.nl
In article <wzfzuxz71g.fsf@localhost.cs.uu.nl>, Piet van Oostrum wrote:
> Why would you want an X11 version? There is a Carbon version
Which is great at the console but no more useful than the preinstalled
one if you're connected remotely,
> which is nicer.
In some ways.
Unless you're running a pure standalone system it's a good idea to
have both. The only tricky bit about that is conditionalizing the
startup files, in case you want the environment to be different for
the two cases.
Which leads me to a new question: is there a variable or function
which identifies the carbon build? At the moment I'm using
(fboundp 'do-applescript)
which really feels like hack. Is there a cleaner check?
--
d f-d
next prev parent reply other threads:[~2002-10-23 13:01 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1035334713.26558.help-gnu-emacs@gnu.org>
2002-10-23 8:54 ` installing emacs and X11 on OS X Joseph Kiniry
2002-10-23 12:04 ` Michael Hudson
2002-10-23 12:14 ` Piet van Oostrum
2002-10-23 13:01 ` Hugo Wolf [this message]
2002-10-23 14:08 ` John Paul Wallington
2002-10-24 5:47 ` Eli Zaretskii
2002-10-24 12:43 ` Hugo Wolf
2002-10-24 17:27 ` Eli Zaretskii
[not found] ` <mailman.1035484120.27029.help-gnu-emacs@gnu.org>
2002-10-24 20:01 ` Schone Mullerin
2002-10-26 7:17 ` Eli Zaretskii
[not found] ` <mailman.1035620182.18482.help-gnu-emacs@gnu.org>
2002-10-26 14:39 ` Hugo Wolf
2002-10-26 14:13 ` Eli Zaretskii
[not found] ` <mailman.1035645140.22359.help-gnu-emacs@gnu.org>
2002-10-26 21:41 ` Hugo Wolf
2002-10-26 21:43 ` Eli Zaretskii
[not found] ` <mailman.1035672257.29530.help-gnu-emacs@gnu.org>
2002-10-27 15:07 ` Hugo Wolf
2002-10-27 15:53 ` Eli Zaretskii
2002-10-27 16:14 ` Piet van Oostrum
2002-10-27 19:47 ` Hugo Wolf
2002-10-27 19:13 ` Thomas F. Burdick
2002-10-27 19:53 ` Hugo Wolf
2002-10-28 6:00 ` Eli Zaretskii
[not found] ` <mailman.1035737630.1161.help-gnu-emacs@gnu.org>
2002-10-27 20:08 ` Hugo Wolf
2002-10-27 20:33 ` Chris Lott
2002-10-23 12:53 ` Hugo Wolf
[not found] <mailman.1035870384.15595.help-gnu-emacs@gnu.org>
2002-10-29 13:42 ` Hugo Wolf
2002-10-29 17:14 ` Kevin Rodgers
2002-10-29 19:45 ` Eli Zaretskii
[not found] ` <mailman.1035924328.7472.help-gnu-emacs@gnu.org>
2002-10-29 21:17 ` Schone Mullerin
[not found] <mailman.1035784882.23705.help-gnu-emacs@gnu.org>
2002-10-28 12:45 ` Hugo Wolf
2002-10-28 18:18 ` Eli Zaretskii
[not found] ` <mailman.1035832709.18867.help-gnu-emacs@gnu.org>
2002-10-28 20:15 ` Schone Mullerin
2002-10-29 5:45 ` Eli Zaretskii
2002-10-28 21:25 ` Thomas F. Burdick
2002-10-29 5:55 ` Eli Zaretskii
2002-10-29 15:41 ` Stefan Monnier <foo@acm.com>
2002-10-29 19:48 ` Eli Zaretskii
[not found] ` <mailman.1035924479.14908.help-gnu-emacs@gnu.org>
2002-10-29 20:57 ` Stefan Monnier <foo@acm.com>
[not found] <mailman.1035438509.9019.help-gnu-emacs@gnu.org>
2002-10-24 6:59 ` John Paul Wallington
2002-10-23 0:53 Hugues Joly
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='L4xt9.68493$qM2.19402@sccrnsc02' \
--to=hwolf@deutsches.lieder.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).