unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 36945@debbugs.gnu.org, Fabrice Popineau <fabrice.popineau@gmail.com>
Subject: bug#36945: 27.0.50; read-library-name
Date: Tue, 15 Sep 2020 15:32:19 +0000 (UTC)	[thread overview]
Message-ID: <e527e74f-5453-42b2-94a7-ba2ea4a9ce97@default> (raw)
In-Reply-To: <87a6xr9q4l.fsf@gnus.org>

> Hm...  perhaps the function is just misnamed.  When I want to find a
> library, I really do want to complete over the library's name, and
> nothing else.  What read-library-name does, however, is file name
> completion over load-path, which is something a bit different.

I don't think the name is bad.  It's just that we have
different ideas of what a "library name" is.  The same
thing happens with file names.  You're talking about a
sort of "base" name.

My suggestion: Improve the `read-library-name' doc to
make clear what it does (whatever you think isn't clear
enough).  And then provide another function that does
what you were wanting/expecting.

Or if you find an easy way to get the behavior you want
as optional behavior by tweaking `read-library-name',
make that change, so the same function can do both things.





      parent reply	other threads:[~2020-09-15 15:32 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
2020-09-17 16:41         ` Stefan Monnier
2020-09-15 15:32     ` Drew Adams [this message]

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=e527e74f-5453-42b2-94a7-ba2ea4a9ce97@default \
    --to=drew.adams@oracle.com \
    --cc=36945@debbugs.gnu.org \
    --cc=fabrice.popineau@gmail.com \
    --cc=larsi@gnus.org \
    --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).