From: Manuel Giraud via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sbaugh@catern.com, emacs-devel@gnu.org
Subject: Re: source-directory, installed Emacs, and C source
Date: Wed, 25 Oct 2023 20:12:02 +0200 [thread overview]
Message-ID: <87y1fqd11p.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83lebqissx.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 25 Oct 2023 19:13:34 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
[...]
> There's no such "consistency" in Emacs. The "consistency" we support
> is that the Lisp files are expected to be in the installed tree. If
> they are there, I see no reason to look for them in any other
> directory, and you didn't provide any real reason. I originally
> thought that you want to remove the *.el files from the installation
> tree, but now I understand you don't, and I'm therefore completely
> baffled about the your feature request.
I think I may have a use case: if you are working *on* Emacs
development. I kind of know when my current running Emacs is in sync
with its source directory. So if I want to work on some feature it is
easier to jump directly files into the source directory and start
modifying those files. This way those modifications are directly
tracked by git in preparation of a future patch.
But maybe I'm just doing it wrong.
--
Manuel Giraud
next prev parent reply other threads:[~2023-10-25 18:12 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. [this message]
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
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
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=87y1fqd11p.fsf@ledu-giraud.fr \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=manuel@ledu-giraud.fr \
--cc=sbaugh@catern.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 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).