all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 14680@debbugs.gnu.org
Subject: bug#14680: 24.3.50; `locate-file-completion' gives wrong candidates - *.elc.elc and no *.el
Date: Mon, 29 Aug 2016 21:44:35 -0400	[thread overview]
Message-ID: <8760qjqbcs.fsf@users.sourceforge.net> (raw)
In-Reply-To: <1b2674c2-42f0-47de-a391-bd3a070f7ac0@default> (Drew Adams's message of "Fri, 29 Apr 2016 10:01:40 -0700 (PDT)")

tags 14680 unreproducible
quit

Drew Adams <drew.adams@oracle.com> writes:
> Yes, it is reproducible (on MS Windows, at least), using (at least)
> Emacs 24 and an Emacs 25 build of a month or so ago.
>
> However, the recipe should have said to do this also, before 
> evaluating the `completing-read' sexp:
>
> (load-library "find-func")

Not able to reproduce on Windows 10; Emacs 24.3, 24.4, 24.5, 25.1-rc1

I tested in a directory with contents:

C:\Users\npostavs\src\emacs>dir /b bug-14680-locate-file-completion
bug-14680.el
isearch+.el
isearch+.elc
isearch+.el~

Evaluated the following from emacs -Q:

(load-library "find-func")
(add-to-list 'load-path ".")
(completing-read "Library name: "
                 'locate-file-completion
                 (cons load-path (find-library-suffixes))
                 nil nil nil (thing-at-point 'symbol))

I got

Possible completions are:
isearch+
isearch+.elc
isearch+.el~






  reply	other threads:[~2016-08-30  1:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:15 bug#14680: 24.3.50; `locate-file-completion' gives wrong candidates - *.elc.elc and no *.el Drew Adams
2016-04-28 23:58 ` Lars Ingebrigtsen
2016-04-29 17:01   ` Drew Adams
2016-08-30  1:44     ` npostavs [this message]
2016-08-30  2:24       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760qjqbcs.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=14680@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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.