From: Leo <sdl.web@googlemail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
Subject: Re: PATCH: Fix IDO interaction with uniquify.el
Date: Wed, 5 May 2010 18:56:21 +0100 [thread overview]
Message-ID: <h2n20a0c1021005051056p37d9a162m36701031068e564e@mail.gmail.com> (raw)
In-Reply-To: <x2hf7ccd24b1005050947p9e29458es149dc129990d1a19@mail.gmail.com>
> What does exactly mean "kill virtual buffers"? If you mean removing
> them from the buffer list, are you going to maintain a separate list,
> instead of regenerating it from recentf-list anew for each
> ido-switch-buffer, or are you going to modify recentf-list?
'kill virtual buffers' means removing them from recentf-list i.e. they
cease to be virtual buffers. So the latter.
> As for the duplicate entries, have you implemented it without using
> uniquify? That does not seem too hard, and it's definitely cleaner.
John and I have discussed whether uniquify should be used. He wants
the virtual buffer name to follow the same style as that from
uniquify. But in order to use unquify, some changes need to be made
since at the moment uniquify is buffer oriented and virtual buffers
are not buffers. Secondly to uniquify completely, the full list of
files with same base name must be known and this adds complexity. I
locally have a patch that completely handles duplicate basenames
(about 40 lines of elisp without using caching) without using uniquify
so I have some idea about the complexity.
In the end we decide temporarily just adding some number
(customisable) of parent directory. In practice one level of parent
directory already significantly removes the chance of a file in
recentf-list being ignored.
> Juanma
Leo
next prev parent reply other threads:[~2010-05-05 17:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 10:27 PATCH: Fix IDO interaction with uniquify.el Óscar Fuentes
2010-01-18 10:59 ` Juanma Barranquero
2010-01-18 11:12 ` Juanma Barranquero
2010-01-18 14:13 ` Óscar Fuentes
2010-01-18 14:32 ` Juanma Barranquero
2010-01-18 14:41 ` Óscar Fuentes
2010-01-18 15:44 ` Chong Yidong
2010-01-18 17:35 ` Óscar Fuentes
2010-01-18 17:52 ` Óscar Fuentes
2010-01-18 18:06 ` Chong Yidong
2010-01-18 19:17 ` Juanma Barranquero
2010-05-05 8:27 ` Leo
2010-05-05 9:56 ` Juanma Barranquero
2010-05-05 12:40 ` Leo
2010-05-05 16:47 ` Juanma Barranquero
2010-05-05 17:35 ` Leo
2010-05-05 19:12 ` Leo
2010-05-05 19:48 ` Juanma Barranquero
2010-05-06 12:54 ` Stefan Monnier
2010-05-05 17:56 ` Leo [this message]
2010-05-05 19:25 ` Juanma Barranquero
2010-05-05 18:14 ` Stefan Monnier
2010-05-05 19:09 ` Óscar Fuentes
2010-05-05 19:50 ` Leo
2010-05-05 19:59 ` Leo
2010-05-05 20:36 ` Óscar Fuentes
2010-05-06 20:43 ` Juri Linkov
2010-05-05 20:27 ` Stefan Monnier
2010-05-05 20:38 ` Óscar Fuentes
2010-05-06 16:56 ` Kim F. Storm
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=h2n20a0c1021005051056p37d9a162m36701031068e564e@mail.gmail.com \
--to=sdl.web@googlemail.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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.