all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: sbaugh@catern.com, emacs-devel@gnu.org
Subject: Re: source-directory, installed Emacs, and C source
Date: Wed, 25 Oct 2023 21:32:35 +0300	[thread overview]
Message-ID: <83edhiimd8.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWYhDuUP--+y71YVCwW0R=mLk7DYGcbR3-YCFgmocB-71Q@mail.gmail.com> (message from chad on Wed, 25 Oct 2023 13:43:01 -0400)

> From: chad <yandros@gmail.com>
> Date: Wed, 25 Oct 2023 13:43:01 -0400
> Cc: emacs-devel@gnu.org
> 
> I don't run under macOS any more, but when I did, there was an extra wrinkle here: emacs typically
> builds as an "app bundle", essentially a directory named "Emacs.app" that contains all of the stuff
> that a typical unix-like installation would put in various subdirs of /usr/local. This was actually quite
> nice -- it meant that I could have a complete, functional version of emacs in both Emacs.app and
> Emacs-old.app whenever I wanted to try something new without stranding myself if the new thing
> turned out to be broken.

??? The "Unix-like" installation puts these files in version-specific
directories, so you can have several Emacs versions available on the
same system at the same time.  I do that all the time, and have about
a dozen Emacs versions installed and runnable.



  reply	other threads:[~2023-10-25 18:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 14:31 source-directory, installed Emacs, and C source sbaugh
2023-10-24 14:47 ` Eli Zaretskii
2023-10-24 15:13   ` Spencer Baugh
2023-10-24 16:00     ` Eli Zaretskii
2023-10-24 16:20       ` sbaugh
2023-10-24 18:34         ` Eli Zaretskii
2023-10-25  8:41           ` Manuel Giraud via Emacs development discussions.
2023-10-25 12:43             ` Eli Zaretskii
2023-10-25 13:20               ` Manuel Giraud via Emacs development discussions.
2023-10-25 13:43                 ` sbaugh
2023-10-25 13:59                   ` Eli Zaretskii
2023-10-25 14:29                     ` sbaugh
2023-10-25 16:13                       ` Eli Zaretskii
2023-10-25 18:12                         ` Manuel Giraud via Emacs development discussions.
2023-10-25 18:37                           ` Eli Zaretskii
2023-10-25 19:07                             ` Manuel Giraud via Emacs development discussions.
2023-10-25 16:59                       ` Emanuel Berg
2023-10-24 18:35         ` Emanuel Berg
2023-10-25 17:43         ` chad
2023-10-25 18:32           ` Eli Zaretskii [this message]
2023-10-25 20:30             ` chad
2023-10-26  4:57               ` Eli Zaretskii
2023-10-25 18:57           ` Manuel Giraud via Emacs development discussions.
2023-10-24 16:00 ` Manuel Giraud via Emacs development discussions.
2023-10-24 16:04   ` Eli Zaretskii
2023-10-24 18:06   ` Emanuel Berg
2023-10-24 18:48   ` Arsen Arsenović
2023-10-24 18:01 ` Manuel Giraud via Emacs development discussions.

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83edhiimd8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sbaugh@catern.com \
    --cc=yandros@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.