unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Leo <sdl.web@googlemail.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 21:25:01 +0200	[thread overview]
Message-ID: <r2rf7ccd24b1005051225pcbd81880q73e6535a7c0b0f80@mail.gmail.com> (raw)
In-Reply-To: <h2n20a0c1021005051056p37d9a162m36701031068e564e@mail.gmail.com>

On Wed, May 5, 2010 at 19:56, Leo <sdl.web@googlemail.com> wrote:

> 'kill virtual buffers' means removing them from recentf-list i.e. they
> cease to be virtual buffers. So the latter.

I don't like that. Virtual buffers and recentf are different user
facilities, and the fact that virtual buffers *use* recentf is just to
simplify its implementation, IMO. Killing a virtual buffer on
ido-switch-buffer and having the file list on File / Open Recent
change seems uncalled for.

> I locally have a patch that completely handles duplicate basenames
> (about 40 lines of elisp without using caching) without using uniquify

FWIW, that's my preference. I use uniquify, but what you show in the
modeline and what you do prefer on a completion list isn't necessarily
the same thing.

> 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.

I don't think so. If you're editing C:/repo/trunk/lisp/bs.el and
C:/repo/emacs-23/lisp/bs.el, you'd need at least two. Why did you
choose this instead of your 40-line complete fix?

    Juanma




  reply	other threads:[~2010-05-05 19:25 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
2010-05-05 19:25                               ` Juanma Barranquero [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=r2rf7ccd24b1005051225pcbd81880q73e6535a7c0b0f80@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@googlemail.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).