From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20968@debbugs.gnu.org
Subject: bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file'
Date: Sat, 4 Jul 2015 11:54:20 -0700 (PDT) [thread overview]
Message-ID: <a938c9a2-814e-42fe-9cd8-64297116d478@default> (raw)
In-Reply-To: <<831tgnye3x.fsf@gnu.org>>
> > > > But AFAIK, the behavior is well-defined.
> > >
> > > It's well-defined only for the current behavior, where the *.el
> > > and the corresponding *.elc files live in the same directory.
> >
> > How so? Please give a concrete example where it is not well-
> > defined for a foo.el and a foo.elc that are in different
> > directories. Explain what problems you think arise in such a case.
>
> I already did that: we search load-path linearly, only once, looking
> for .el and .elc files in each directory.
And the problem with that is...?
> > Can you please point out just what the problems are?
>
> Sorry, don't have all that time.
Then let's please move along.
next prev parent reply other threads:[~2015-07-04 18:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<dc02c2ca-d069-4559-820d-fbd6dfaed9d3@default>
[not found] ` <<83615zyiuq.fsf@gnu.org>
2015-07-04 18:20 ` bug#20968: 25.0.50; Be able to specify the output directory for `byte-compile-file' Drew Adams
2015-07-04 18:25 ` Eli Zaretskii
[not found] ` <<f766b63c-edb1-4f11-9f14-bfcd95d8adcd@default>
[not found] ` <<831tgnye3x.fsf@gnu.org>
2015-07-04 18:54 ` Drew Adams [this message]
[not found] <<23829743-922e-4304-8ab3-b762b8193860@default>
[not found] ` <<74y4iytdjg.fsf@fencepost.gnu.org>
[not found] ` <<e68f1dc9-9e8f-4f54-af8f-a5bb23160576@default>
[not found] ` <<83pp49zb03.fsf@gnu.org>
2015-07-03 14:55 ` Drew Adams
2015-07-04 8:40 ` Eli Zaretskii
2015-07-04 18:48 ` Stefan Monnier
[not found] ` <<d5d5b826-847c-41be-9392-25446b6e37fa@default>
[not found] ` <<83pp48xqm8.fsf@gnu.org>
2015-07-04 14:41 ` Drew Adams
2015-07-04 16:42 ` Eli Zaretskii
2015-07-02 21:05 Drew Adams
2015-07-02 22:12 ` Glenn Morris
2015-07-02 23:51 ` Drew Adams
2015-07-03 12:22 ` Eli Zaretskii
2015-07-03 15:10 ` Stefan Monnier
2015-07-03 17:12 ` Glenn Morris
2015-07-03 17:27 ` Glenn Morris
2015-07-03 17:49 ` Eli Zaretskii
2015-07-03 22:48 ` Artur Malabarba
2015-07-04 8:24 ` Eli Zaretskii
2015-07-04 10:38 ` Alexis
2015-07-04 11:55 ` Eli Zaretskii
2015-07-04 11:10 ` Artur Malabarba
2015-07-04 11:56 ` Eli Zaretskii
2015-07-04 18:46 ` Stefan Monnier
2015-07-04 18:55 ` Eli Zaretskii
2015-07-04 19:26 ` Stefan Monnier
2015-07-04 19:31 ` Eli Zaretskii
2015-07-05 11:54 ` Dmitry Gutov
2015-07-05 14:35 ` Eli Zaretskii
2015-07-05 14:54 ` Dmitry Gutov
2015-07-05 15:18 ` Eli Zaretskii
2015-07-05 15:54 ` Artur Malabarba
2015-07-05 21:56 ` Richard Stallman
2016-04-30 20:07 ` 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
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=a938c9a2-814e-42fe-9cd8-64297116d478@default \
--to=drew.adams@oracle.com \
--cc=20968@debbugs.gnu.org \
--cc=eliz@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 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).