From: Rick Frankel <rick@rickster.com>
To: Axel Kielhorn <org-mode@axelkielhorn.de>
Cc: Org-Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: emacs24-starter-kit and Aquamacs 3.0
Date: Thu, 15 May 2014 09:01:48 -0400 [thread overview]
Message-ID: <a4c00fd5a18a4d2e0b044e6794cfd652@mail.rickster.com> (raw)
In-Reply-To: <6DEC36B6-C61B-45B2-8A30-1EC16C14F173@axelkielhorn.de>
On 2014-05-15 07:59, Axel Kielhorn wrote:
> I never wanted to learn Emacs.
> There is probably a more elegant way to add a /.emacs.d to the path
> when the editor is Aquamacs, but I have to learn some elisp for that.
>
> Or a way to tell Aquamacs to use a different init file.
>
> Any suggestions are appreciated.
Probably not the answer you want, but as a long-time mac and emacs
user, my suggestion would be to use the vanilla os x version of emacs.
IMHO, there is no longer any compelling reason to use aquamacs. It was
started at a time when the core gnu emacs did not support os x, this
is no longer the case.
The "nextstep" build of emacs runs as a native app, supports
anti-aliased fonts, etc. Personally, i find that the keyboard
rebinding in aquamacs just make it it harder to use/learn emacs, as
all the documentation, etc, is based on the standard, cross-platform
bindings. Once you learn them, you will be able to use emacs on any
platform -- mac, windows, unix. Also, your configuration will be
portable across all the same platforms.
rick
next prev parent reply other threads:[~2014-05-15 13:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 11:59 emacs24-starter-kit and Aquamacs 3.0 Axel Kielhorn
2014-05-15 13:01 ` Rick Frankel [this message]
2014-05-15 14:28 ` Axel Kielhorn
2014-05-15 14:31 ` Vikas Rawal
2014-05-15 17:19 ` Rick Frankel
2014-05-15 18:51 ` Thomas S. Dye
2014-05-15 19:41 ` Vikas Rawal
2014-05-16 1:58 ` Grant Rettke
2014-05-15 17:43 ` Peter Neilson
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4c00fd5a18a4d2e0b044e6794cfd652@mail.rickster.com \
--to=rick@rickster.com \
--cc=emacs-orgmode@gnu.org \
--cc=org-mode@axelkielhorn.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).