From: Leo <sdl.web@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Antoine Levitt <smeuuh@gmail.com>, 2042@debbugs.gnu.org
Subject: bug#2042: Ido-mode : filtering does not keep ordering
Date: Sun, 02 Oct 2011 08:04:30 +0800 [thread overview]
Message-ID: <m18vp4dzsh.fsf@gmail.com> (raw)
In-Reply-To: <8739fch6in.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 01 Oct 2011 15:10:56 -0400")
On 2011-10-02 03:10 +0800, Chong Yidong wrote:
> Leo <sdl.web@gmail.com> writes:
>
>> I occasionally try iswitch-mode and find its buffer switching much
>> more pleasant to use than ido's. The trouble is ido tries to be smart
>> in ordering matches. Sadly that gets in the way most of the time.
>
> Could you explain in words what the existing code tries to do?
>
> Maybe it's indeed misguided and ought to be taken out, but it would be
> good to first figure out what the original intention was.
The existing code gives different precedence to different match type:
full-matches > suffix matches > prefix matches > remaining matches
For example in switching buffers in ido:
input: ab
Buffer: ab[c]{abcd | abc | xabcd | xabc}
now when the user types c, it changes to:
Buffer: abc{abc | abcd | xabcd | xabc}
Note the different ordering of "abcd" and "abc". Because typing is so
much quicker than observing the new order, one usually mis-chooses a
match.
Thus, the above strategy may break down when the original ordering is
meaningful for example, (buffer-list) returns a list in order of
recency.
Leo
next prev parent reply other threads:[~2011-10-02 0:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 13:54 bug#2042: Ido-mode : filtering does not keep ordering Antoine Levitt
2011-09-24 16:20 ` Leo
2011-09-25 8:54 ` Antoine Levitt
2011-10-01 19:10 ` Chong Yidong
2011-10-02 0:04 ` Leo [this message]
2011-10-29 6:38 ` Chong Yidong
2011-10-29 7:06 ` Leo
2012-09-16 9:29 ` Matthew Woodcraft
2012-09-16 14:55 ` Leo
2012-09-16 15:03 ` Leo
2012-09-16 16:33 ` Chong Yidong
2012-09-16 22:28 ` Leo
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=m18vp4dzsh.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=2042@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=smeuuh@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.