unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Skipping installation of .el.gz files
Date: Tue, 24 Oct 2023 15:35:56 +0300	[thread overview]
Message-ID: <83v8awkxjn.fsf@gnu.org> (raw)
In-Reply-To: <ierh6mhdr1n.fsf@janestreet.com> (message from Spencer Baugh on Mon, 23 Oct 2023 16:25:56 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Mon, 23 Oct 2023 16:25:56 -0400
> 
> > No, because the source directory could hold code different from the
> > one which was used to install the files under /usr/share.  Think about
> > Emacs installed from a Git repository that got many updates after
> > that, for example.
> 
> Yes.  And this is an issue today for jumping to the definitions of
> functions in C files, since those are not packaged with Emacs.  Today,
> that is broken out of the box if source-directory is still around.

"Broken" is an exaggeration.  C source files are less important that
Lisp sources, and in many cases the C sources are not installed at all
on the user's machine.  I see no problem here.

> So if you think this behavior is bad

I didn't say it was bad, I said your suggestion for a change was not a
good idea, since it would introduce a problem where currently there is
none.

> then should we fix it to not happen for the case of C files?
> Perhaps by clearing source-directory when Emacs is installed, so
> that Emacs cannot find obsolete C files out of the Git repository?

This problem doesn't exist for most users, so I see no reason to fix
something that isn't broken.



  parent reply	other threads:[~2023-10-24 12:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23  0:45 Skipping installation of .el.gz files Spencer Baugh
2023-10-23  5:55 ` Emanuel Berg
2023-10-23  6:41 ` Corwin Brust
2023-10-23 16:18   ` Spencer Baugh
2023-10-23 11:35 ` Eli Zaretskii
2023-10-23 12:28   ` Emanuel Berg
2023-10-28 10:44     ` Eli Zaretskii
2023-10-28 10:52       ` Emanuel Berg
2023-10-23 16:42   ` Spencer Baugh
2023-10-23 18:39     ` Eli Zaretskii
2023-10-23 20:25       ` Spencer Baugh
2023-10-23 20:57         ` Emanuel Berg
2023-10-24 12:35         ` Eli Zaretskii [this message]
2023-10-24 12:49           ` Emanuel Berg

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=83v8awkxjn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@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.
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).