From: Alex Kosorukoff <alex@3form.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 17467 <17467@debbugs.gnu.org>
Subject: bug#17467: 24.3; locate-library returning spurious path
Date: Sun, 11 May 2014 18:35:54 -0700 [thread overview]
Message-ID: <CAHD9_tTWLY8FnzCBQ18rHix+CmcNYhaD3B-+N_4ednq5QkRE+Q@mail.gmail.com> (raw)
In-Reply-To: <ekiopbbzv0.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
Thank you for the example. You are right, gnus-start.el is using
locate-library to check existence of its init files and uses load to search
for them again right after. Given how that code is written, we probably
should keep locate-library as is since at least some people people are
relying on its ability to locate arbitrary files that are not libraries.
On Sun, May 11, 2014 at 5:32 PM, Glenn Morris <rgm@gnu.org> wrote:
> Alex Kosorukoff wrote:
>
> > I think these file names are more appropriate for data files, not
> > executable ones. It is undesirable that a name "tramp.gz" will shadow a
> > valid library file "tramp.elc" that won't be found as a result. When you
> > say those names aren't spurious, do you have a particular example of an
> > emacs elisp library in mind which file name ends with a suffix other than
> > .el .elc .el.gz .elc.gz? I think the main difference is that I assume
> that
> > this list is exhaustive and you imply that it is not. You can prove me
> > wrong by a single example.
>
> I've somewhat lost track of exactly what you want an example of, but:
>
> When Gnus starts, it will read the `gnus-site-init-file'
> (`.../site-lisp/gnus-init' by default) and `gnus-init-file' (`~/.gnus'
> by default) files. These are normal Emacs Lisp files and can be used
> to avoid cluttering your `~/.emacs' and `site-init' files with Gnus
> stuff. Gnus will also check for files with the same names as these,
> but with `.elc' and `.el' suffixes. In other words, if you have set
> `gnus-init-file' to `~/.gnus', it will look for `~/.gnus.elc',
> `~/.gnus.el', and finally `~/.gnus' (in this order).
>
> and it uses locate-library to do that.
>
[-- Attachment #2: Type: text/html, Size: 2227 bytes --]
next prev parent reply other threads:[~2014-05-12 1:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 16:06 bug#17467: 24.3; locate-library returning spurious path Alex Kosorukoff
2014-05-11 17:03 ` Eli Zaretskii
2014-05-11 17:38 ` Alex Kosorukoff
2014-05-11 17:46 ` Eli Zaretskii
2014-05-11 17:53 ` Alex Kosorukoff
2014-05-11 18:10 ` Eli Zaretskii
2014-05-11 18:55 ` Alex Kosorukoff
2014-05-11 22:55 ` Stefan Monnier
2014-05-12 0:41 ` Alex Kosorukoff
2014-05-11 17:37 ` Glenn Morris
2014-05-11 17:43 ` Alex Kosorukoff
2014-05-11 19:50 ` Stefan Monnier
2014-05-11 20:45 ` Alex Kosorukoff
2014-05-11 21:00 ` Alex Kosorukoff
2014-05-11 21:19 ` Glenn Morris
2014-05-11 22:31 ` Alex Kosorukoff
2014-05-11 21:56 ` Stefan Monnier
2014-05-12 0:20 ` Alex Kosorukoff
2014-05-12 0:32 ` Glenn Morris
2014-05-12 1:35 ` Alex Kosorukoff [this message]
2014-05-12 2:02 ` Alex Kosorukoff
2014-05-12 2:18 ` Stefan Monnier
2014-05-12 4:36 ` Alex Kosorukoff
2014-05-12 6:39 ` Stefan Monnier
2014-05-12 17:46 ` Alex Kosorukoff
2020-08-25 10:39 ` Lars Ingebrigtsen
2020-08-25 14:22 ` Stefan Monnier
2020-08-25 14:25 ` Lars Ingebrigtsen
2020-10-13 1:41 ` Lars Ingebrigtsen
2014-05-15 19:39 ` Stefan Monnier
2014-05-15 23:57 ` Alex Kosorukoff
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=CAHD9_tTWLY8FnzCBQ18rHix+CmcNYhaD3B-+N_4ednq5QkRE+Q@mail.gmail.com \
--to=alex@3form.com \
--cc=17467@debbugs.gnu.org \
--cc=rgm@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.