From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.devel Subject: Re: PATCH: Fix IDO interaction with uniquify.el Date: Wed, 5 May 2010 21:25:01 +0200 Message-ID: References: <87k4vf1zdh.fsf@telefonica.net> <87tyujz57h.fsf@telefonica.net> <87ockrz4eu.fsf@telefonica.net> <87pr57uw25.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1273102210 18490 80.91.229.12 (5 May 2010 23:30:10 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 5 May 2010 23:30:10 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org To: Leo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu May 06 01:30:07 2010 connect(): No such file or directory Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1O9o2Y-00008F-KG for ged-emacs-devel@m.gmane.org; Thu, 06 May 2010 01:30:06 +0200 Original-Received: from localhost ([127.0.0.1]:51396 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O9o2X-0004yE-BH for ged-emacs-devel@m.gmane.org; Wed, 05 May 2010 19:30:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1O9kDl-0005aE-KI for emacs-devel@gnu.org; Wed, 05 May 2010 15:25:25 -0400 Original-Received: from [140.186.70.92] (port=39137 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1O9kDk-0005Yl-4l for emacs-devel@gnu.org; Wed, 05 May 2010 15:25:25 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1O9kDi-0004xF-FD for emacs-devel@gnu.org; Wed, 05 May 2010 15:25:24 -0400 Original-Received: from mail-bw0-f225.google.com ([209.85.218.225]:58095) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1O9kDi-0004xB-6S for emacs-devel@gnu.org; Wed, 05 May 2010 15:25:22 -0400 Original-Received: by bwz25 with SMTP id 25so3289941bwz.8 for ; Wed, 05 May 2010 12:25:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=q6BzxhdR4o7q9wHwUQXK0y0KJ29XVp0PnWo7NfmjzLE=; b=ZZuI96o2OvN6oWLOnuoWAxmmGIaqzENCaeTNALFxuXv1HI6AgzfvaL+f6eN+g/b9Nr 8XmqOZV70YfKuerk2Sp8gfeICf+zZZYH+38VcRbQ9ENNzlSphCEXHpzAlPvnZInUzlcT F9V96gQqjT+HCvYkZINpy5AH1CcUEfvDln/RY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=G5RjqdDGIxLMRIejM7oNQeKi0xvA1lXR/fNF/vpELzNhGUlF6DsgSlVKiQ63IVvAQ5 AsBfQBWpTKSszcTWpRfYSZpBPDxH5TT5EJP+/yVy40RpRO/KuXqyB1dtCJ6q7sJcrH2g g5zaQPAQHJEWLAuoSNJL13cxVyR9xaXPUMP/M= Original-Received: by 10.204.154.153 with SMTP id o25mr4068915bkw.68.1273087521124; Wed, 05 May 2010 12:25:21 -0700 (PDT) Original-Received: by 10.204.84.81 with HTTP; Wed, 5 May 2010 12:25:01 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:124562 Archived-At: On Wed, May 5, 2010 at 19:56, Leo 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