From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: ido slow for outline path completion Date: Mon, 22 Dec 2008 09:30:57 +0100 Message-ID: References: <20524da70812121204x9a23736g5a03f8a04d8213d5@mail.gmail.com> <67E6FD56-F95F-4EEB-8BC3-4ED566B2ECAB@uva.nl> <20524da70812181557m79252c30hc941fe5965f917e8@mail.gmail.com> <20524da70812211324p25462f1y83d70f1acd655a2d@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LEgBu-0004CK-2u for emacs-orgmode@gnu.org; Mon, 22 Dec 2008 03:31:06 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LEgBr-0004C8-IT for emacs-orgmode@gnu.org; Mon, 22 Dec 2008 03:31:04 -0500 Received: from [199.232.76.173] (port=49944 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LEgBr-0004C5-Cr for emacs-orgmode@gnu.org; Mon, 22 Dec 2008 03:31:03 -0500 Received: from mx20.gnu.org ([199.232.41.8]:40121) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LEgBq-0000m8-TH for emacs-orgmode@gnu.org; Mon, 22 Dec 2008 03:31:03 -0500 Received: from ug-out-1314.google.com ([66.249.92.172]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LEgBq-0006mW-2t for emacs-orgmode@gnu.org; Mon, 22 Dec 2008 03:31:02 -0500 Received: by ug-out-1314.google.com with SMTP id 36so853719uga.17 for ; Mon, 22 Dec 2008 00:31:00 -0800 (PST) In-Reply-To: <20524da70812211324p25462f1y83d70f1acd655a2d@mail.gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Samuel Wales Cc: emacs-orgmode@gnu.org On Dec 21, 2008, at 10:24 PM, Samuel Wales wrote: > Hi Carsten, > > I just meant that there are 3 path completion entry points > (remember, which can also use refile; refile; and goto), and > they are similar, but are specified differently > (e.g. maxlevel variable in goto and alist in refile). So, > maybe there is a way to make the syntax for specifying them > consistent for new users. > Perhaps goto can use refile's path selection subsystem. > That allows basename flex matching (by turning off > org-refile-use-outline-path, useful for me as an interim workaround > for ido > bugs) and other stuff like specifying the list of files to > search. Hi Samuel, org-goto is different because it only goes to the current file. Refile was originally meant to go to a selected class of headings. You can use the refile command itself including its setup to *go* some place by calling org-refile with a prefix argument. A double prefix will make the command jump directly to the location where the last refile event delivered its content. - Carsten > By the way, if you type "?" a few times using ido, it will > show a completions buffer. But here's the interesting part: > that showed one path, which was "mytodo//" plus the full > path name of the file -- not the outline path. M might > be another clue? I have no time to debug ido, I am afraid, unless you can show that the table I pass to ido is invalid.