all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sbaugh@catern.com
To: emacs-devel@gnu.org
Subject: Re: source-directory, installed Emacs, and C source
Date: Tue, 24 Oct 2023 12:20:56 -0400	[thread overview]
Message-ID: <87y1fsq9ef.fsf@catern.com> (raw)
In-Reply-To: 837cncko34.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:
>> From: Spencer Baugh <sbaugh@janestreet.com>
>> Date: Tue, 24 Oct 2023 11:13:33 -0400
>> 
>> > Why would the Lisp sources not be available where Emacs installs them,
>> > i.e. in the /usr/share tree?
>> 
>> If the user ./configure'd Emacs to not install them because they prefer
>> to jump to source-directory instead.  That's what I meant by:
>
> How do you configure Emacs not to install the Lisp files?  And why?
>
>> >This would be a great improvement for users who keep source-directory
>> >around (since now Emacs jumps straight to your source repo, allowing
>> >easy modifications, and also you can skip installing Lisp source files
>> >with Emacs)
>
> Emacs is supposed to be installed _with_ Lisp files.  It is important
> to let users modify the Lisp files when they need.  So I'm not sure we
> want to support an installation where Lisp files are not available.

Yes, to be clear, I'm talking about a case where the Lisp files are in
source-directory, not where they don't exist at all.  If the Lisp files
are in source-directory and stay around there, then perhaps they don't
need to be copied to /usr/share.

But if we want to always copy them to /usr/share, that's fine, it's not
necessary to support skipping that.

My suggestion, then, is that we should allow customizing Emacs to prefer
jumping to source-directory over jumping to the installed copies of the
Lisp files.




  reply	other threads:[~2023-10-24 16:20 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 [this message]
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
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=87y1fsq9ef.fsf@catern.com \
    --to=sbaugh@catern.com \
    --cc=emacs-devel@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 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.