From: Leo <sdl.web@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: John Wiegley <jwiegley@gmail.com>, "Kim F. Storm" <storm@cua.dk>,
emacs-devel@gnu.org
Subject: Re: Concerning the new `ido-use-virtual-buffers' feature
Date: Thu, 27 May 2010 19:01:04 +0100 [thread overview]
Message-ID: <AANLkTim6Exme9zKKnceqzmgPljWQBves1Z0AALZr4yW3@mail.gmail.com> (raw)
In-Reply-To: <201005271257.02056.tassilo@member.fsf.org>
Hello all,
On 27 May 2010 11:57, Tassilo Horn <tassilo@member.fsf.org> wrote:
> On Thursday 27 May 2010 11:56:53 Leo wrote:
>
> Hi Leo, John, Kim,
>
>> Meanwhile feel free to change the patch.
>
> Hm, it doesn't apply to the current bzr trunk. Anyway, I rewrote it to
> be controled by the ido-use-virtual-buffers variable solely with 3
> values 'never, 'auto, and 'always.
>
> The resulting patch is attached. Basically, it works, but there's one
> bug I cannot figure out how to solve. When ido-use-virtual-buffers is
> 'auto and the current input doesn't even match any closed buffer
> (recentf file), then it's stuck instead of displaying [no match].
>
> I don't know ido very well and cannot figure out how to get that right.
> Kim, maybe you could check what's wrong?
I think it is in the added code in ido-exhibit which is run in
post-command-hook if I remember correctly.
When your input doesn't match any (including virtual ones), the code
in ido-exhibit tells ido (the big LOOP in ido-read-internal) to
rebuild the buffer list and there isn't any match so it rebuild again
and again. Go into a infinite loop.
You could try creating a new let-bound variable to detect such a
situation and avoid the infinite loop.
> I have papers on file. I use 7 lines originating from Leo's patch, so I
> don't know if that has to wait till Leo's assignments arrive...
>
> Bye,
> Tassilo
HTH,
Leo
next prev parent reply other threads:[~2010-05-27 18:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 9:56 Concerning the new `ido-use-virtual-buffers' feature Leo
2010-05-27 10:57 ` Tassilo Horn
2010-05-27 18:01 ` Leo [this message]
2010-05-27 19:05 ` Tassilo Horn
2010-05-28 1:21 ` Leo
2010-05-28 1:45 ` Leo
2010-05-28 6:21 ` Tassilo Horn
2010-05-28 9:07 ` Leo
2010-05-28 9:26 ` Leo
2010-05-28 10:35 ` Juanma Barranquero
2010-05-28 12:15 ` Leo
2010-05-28 12:29 ` Tassilo Horn
2010-05-29 14:15 ` Leo
2010-06-01 23:54 ` Juanma Barranquero
2010-06-02 3:28 ` Leo
2010-06-02 5:57 ` Juanma Barranquero
2010-06-02 9:43 ` Leo
[not found] ` <AANLkTilMurdEZBA-kiWHlS9-r0VK6W5v@mail.gmail.com>
2011-10-16 10:06 ` Antoine Levitt
2013-07-06 12:57 ` Leo Liu
[not found] ` <201006020842.48913.tassilo@member.fsf.org>
[not found] ` <AANLkTikTDRtnbzNHTzVlMvHyl0pDHuhpQLu5k8Il4vP0@mail.gmail.com>
2010-06-02 8:29 ` Tassilo Horn
2010-06-02 9:28 ` Juanma Barranquero
2010-06-02 9:55 ` Tassilo Horn
2010-06-02 10:27 ` Juanma Barranquero
-- strict thread matches above, loose matches on Subject: below --
2010-05-26 10:14 Tassilo Horn
2010-05-26 20:59 ` John Wiegley
2010-05-27 6:54 ` Tassilo Horn
2010-05-27 6:57 ` John Wiegley
2010-05-27 8:10 ` Tassilo Horn
2010-05-27 8:26 ` John Wiegley
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=AANLkTim6Exme9zKKnceqzmgPljWQBves1Z0AALZr4yW3@mail.gmail.com \
--to=sdl.web@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@gmail.com \
--cc=storm@cua.dk \
--cc=tassilo@member.fsf.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.