unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: 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 14:32:58 +0200	[thread overview]
Message-ID: <87a6xr9q4l.fsf@gnus.org> (raw)
In-Reply-To: <jwv1rj4yu9n.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 14 Sep 2020 16:46:05 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> ~/.emacs is a common name for a file that can be loaded, so I will
> object to it being "obvious".  Also, while `.git` should preferably not
> be listed, `.git/` arguably could since you might keep Elisp files in
> there.
>
> So I think we should list all directories, but I agree we should
> probably strip away all files whose name doesn't end in `.el`, `.elc`,
> `.el.gz` (and any other such extension in `load-suffixes`), and we
> should ideally only list the extension when it's the only
> remaining choice.

read-library-name has slightly unclear semantics -- I didn't know that
it was supposed to complete over directory names at all.  Perhaps that
should be mentioned in the doc string?

> Oh, and another reason to keep files that don't just end in `.el` is
> when you want to load `foo.el.BAK` or `foo.el~`, so maybe we should only
> skip those files which don't have `.el` somewhere in their name :-(

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.

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





  reply	other threads:[~2020-09-15 12: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 [this message]
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

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=87a6xr9q4l.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36945@debbugs.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).