From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Sam Aaron <samaaron@gmail.com>,
10292@debbugs.gnu.org, "Richard M. Stallman" <rms@gnu.org>
Subject: bug#10292: following symlinks in byte-recompile-directory
Date: Wed, 25 Nov 2020 02:14:15 -0800 [thread overview]
Message-ID: <CADwFkmna4TZOkZyOZye9gDq8hyyFiW0PbxTvibpf4TXxPG2qXA@mail.gmail.com> (raw)
In-Reply-To: <8736hz6mv1.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Sat, 17 Aug 2019 22:53:06 -0700")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Sam Aaron <samaaron@gmail.com> writes:
>
>> I noticed that the implementation of byte-recompile-directory has
>> specific code to not allow symlinks to be followed. As I use symlinks
>> to structure my ~/.emacs.d directory, this means this fn doesn't work
>> for me. Is there any specific motivation for not having the following
>> signature:
>>
>> (byte-recompile-directory-sl DIRECTORY &optional ARG FORCE FOLLOW-SYMLINKS)
>
> (I'm going through old bug reports that unfortunately have gotten no
> responses yet.)
>
> Not following symlinks introduced in 1993, but the commit message
> doesn't explain why:
>
> commit e9681c45f9ffd2819410b763338ba58b0b892b78
> Author: Richard M. Stallman <rms@gnu.org>
> Date: Thu Dec 23 03:37:27 1993 +0000
>
> (byte-compile-dest-file): If FILENAME is not recognized, append .elc to it.
>
> (byte-recompile-directory): Don't treat symlinks as dirs.
>
> (batch-byte-recompile-directory): Add autoload cookie.
>
> Adding a parameter to the function to follow symlinks seems pretty
> harmless, and seems somewhat useful, so I think it should be added.
Yes, I agree.
> Does anybody object to that?
Let's assume no, since there has been no replies in the last year. :-)
next prev parent reply other threads:[~2020-11-25 10:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 14:22 bug#10292: following symlinks in byte-recompile-directory Sam Aaron
2019-08-18 5:53 ` Lars Ingebrigtsen
2020-11-25 10:14 ` Stefan Kangas [this message]
2020-11-26 10:00 ` Lars Ingebrigtsen
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=CADwFkmna4TZOkZyOZye9gDq8hyyFiW0PbxTvibpf4TXxPG2qXA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=10292@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=samaaron@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.