From: David Reitter <david.reitter@gmail.com>
To: sds@gnu.org
Cc: "emacs-devel@gnu.org developers" <emacs-devel@gnu.org>
Subject: Re: mac os x: how do you run emacs in-place?
Date: Wed, 26 Nov 2014 16:36:22 -0500 [thread overview]
Message-ID: <D9976ABC-7ED5-4580-AE34-4BA88608ED52@gmail.com> (raw)
In-Reply-To: <m27fyhwt60.fsf@gnu.org>
On Nov 26, 2014, at 4:25 PM, Sam Steingold <sds@gnu.org> wrote:
> and I don't want to use that, mostly because clicking on file names in
> *Help* buffer finds the installed "el.gz" files instead of the files
> under version control.
Understood. I don’t think what you want exists as an option so far.
>> only the first “make install” is necessary
>
> this is not true because the executable is copied, not symlinked.
I think I am right because a simple “make” will copy it again.
See nextstep/Makefile, line 29 (target ${ns_appbindir}/Emacs, which is required by “all”).
And this makefile is called via the “ns-app” target in src/Makefile, which is put in $OTHER_FILES, required by “all” there (and not just “install”).
> However, you gave me an idea:
> I will go through nextstep/Emacs.app and replace files and directories
> with symlinks back into the tree.
If this works well, you could get the ns-app target to make symlinks in nextstep (put code as a new target in nextstep/Makefile perhaps). Then, “make install” will do what it does now, but if one wants to run the executable directly, this could be conveniently done after a “make”.
next prev parent reply other threads:[~2014-11-26 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-26 19:01 mac os x: how do you run emacs in-place? Sam Steingold
2014-11-26 20:01 ` Harald Hanche-Olsen
2014-11-26 21:17 ` Sam Steingold
2014-11-26 20:56 ` David Reitter
2014-11-26 21:25 ` Sam Steingold
2014-11-26 21:36 ` David Reitter [this message]
2014-11-27 11:00 ` Jan D.
2014-11-28 6:09 ` Sam Steingold
-- strict thread matches above, loose matches on Subject: below --
2014-11-26 20:18 Angelo Graziosi
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=D9976ABC-7ED5-4580-AE34-4BA88608ED52@gmail.com \
--to=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=sds@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).