unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36945@debbugs.gnu.org, fabrice.popineau@gmail.com,
	monnier@iro.umontreal.ca
Subject: bug#36945: 27.0.50; read-library-name
Date: Thu, 17 Sep 2020 16:40:24 +0200	[thread overview]
Message-ID: <875z8cqxev.fsf@gnus.org> (raw)
In-Reply-To: <83sgbj85ak.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Sep 2020 17:48:19 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Since load-library must support the use case when the user forces to
> load the .el file, not the .elc file, read-library-name must allow
> library names with extensions, I think.  IOW, the "library" in this
> context is just the basename of its file name, with or without the
> extension.

Yeah.  So I think the request in 36945 can't be done -- Emacs has to
complete over all files in load-path, no matter what they're called,
really.

I'm not sure what context the request was made in (since it's not
stated), but I thought about it from a `find-library' context.

Which should probably use something like the patch that was reverted,
but put into its own function.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-09-17 14:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  9:48 bug#36945: 27.0.50; read-library-name Fabrice Popineau
2019-08-23  4:55 ` Lars Ingebrigtsen
2019-08-26 14:55   ` Noam Postavsky
2019-08-27  7:48     ` Lars Ingebrigtsen
2022-02-05 23:31     ` Lars Ingebrigtsen
2020-09-14 20:46 ` Stefan Monnier
2020-09-15 12:32   ` Lars Ingebrigtsen
2020-09-15 13:31     ` Stefan Monnier
2020-09-15 14:48     ` Eli Zaretskii
2020-09-17 14:40       ` Lars Ingebrigtsen [this message]
2020-09-17 16:41         ` Stefan Monnier
2020-09-15 15:32     ` Drew Adams

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=875z8cqxev.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36945@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=fabrice.popineau@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).