all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Alexis <flexibeast@gmail.com>
Cc: 25995@debbugs.gnu.org
Subject: bug#25995: 26.0.50; Mismatch between documented and actual behaviour of icomplete
Date: Thu, 09 Mar 2017 18:25:21 -0500	[thread overview]
Message-ID: <87shmm823i.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87a88yveuj.fsf@debian> (Alexis's message of "Mon, 06 Mar 2017 22:12:20 +1100")

tags 25995 confirmed
quit

Alexis <flexibeast@gmail.com> writes:

> * Create a test directory containing three files: '1', '2', '3'.
>
> * Change to that directory and run emacs -Q.
>
> * M-x icomplete-mode
>
> * C-x C-f
>
> * C-j
>
> Section 19.7.2 of the Emacs manual states:
>
> "At any time, you can type ‘C-j’ to select the first completion in the
> list."
>
> Reading left-to-right, '1' is the first item in the list. So C-j
> should visit that file. Instead, it visits '3'.

This seems to have been introduced by [1: 65797b1].  I guess
completion-pcm--filename-try-filter should not reverse its input?

1: 2016-04-28 19:31:43 +0200 65797b1d75e9f608ffd50fd88be47a854b143bb1
  Make icomplete respect `completion-ignored-extensions'

--- i/lisp/minibuffer.el
+++ w/lisp/minibuffer.el
@@ -3257,7 +3257,7 @@ completion-pcm--filename-try-filter
                       "\\)\\'")))
       (dolist (f all)
         (unless (string-match-p re f) (push f try)))
-      (or try all))))
+      (or (nreverse try) all))))
 
 
 (defun completion-pcm--merge-try (pattern all prefix suffix)





  reply	other threads:[~2017-03-09 23:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 11:12 bug#25995: 26.0.50; Mismatch between documented and actual behaviour of icomplete Alexis
2017-03-09 23:25 ` npostavs [this message]
2017-06-19  0:19   ` Dmitry Gutov
2017-06-19  3:28     ` npostavs
2017-06-21  2:04       ` Dmitry Gutov
2017-06-21  2:50         ` npostavs
2017-06-21 22:17           ` Dmitry Gutov

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=87shmm823i.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25995@debbugs.gnu.org \
    --cc=flexibeast@gmail.com \
    /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.