From: Alex Kosorukoff <alex@3form.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17467@debbugs.gnu.org
Subject: bug#17467: 24.3; locate-library returning spurious path
Date: Sun, 11 May 2014 10:53:34 -0700 [thread overview]
Message-ID: <CAHD9_tTj9ydkhf+XFWCphq=RLfGiwnxbECJx1noqsNUxTcyyvQ@mail.gmail.com> (raw)
In-Reply-To: <8338ggus2g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
I am not sure what use case did you mean exactly.
(locate-library "tramp.el.gz" 'nosuffix) will return the path to
tramp.el.gz as expected
did you mean the following
(locate-library "tramp.el") returning the path to tramp.el.gz?
On Sun, May 11, 2014 at 10:46 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Alex Kosorukoff <alex@3form.com>
> > Date: Sun, 11 May 2014 10:38:39 -0700
> > Cc: 17467@debbugs.gnu.org
> >
> > I think locate-library has an extra parameter nosuffix, so
> (locate-library
> > "tramp.el" 'nosuffix) will find "tramp.el." I guess for backward
> > compatibility we can set nosuffix to t whenever the name has a valid
> suffix
> > already.
>
> But what about adding ".gz" to it?
>
> In any case, it is very convenient to not have to worry whether
> there's already a suffix there. You cannot always know that when user
> input is involved.
>
[-- Attachment #2: Type: text/html, Size: 1517 bytes --]
next prev parent reply other threads:[~2014-05-11 17:53 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 [this message]
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
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
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='CAHD9_tTj9ydkhf+XFWCphq=RLfGiwnxbECJx1noqsNUxTcyyvQ@mail.gmail.com' \
--to=alex@3form.com \
--cc=17467@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).