emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ido slow for outline path completion
Date: Mon, 22 Dec 2008 09:30:57 +0100	[thread overview]
Message-ID: <A733F4DC-5CED-4258-9536-FC80932584C9@uva.nl> (raw)
In-Reply-To: <20524da70812211324p25462f1y83d70f1acd655a2d@mail.gmail.com>

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.

  reply	other threads:[~2008-12-22  8:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 20:04 ido slow for outline path completion Samuel Wales
2008-12-15  9:36 ` Carsten Dominik
2008-12-18 23:57   ` Samuel Wales
2008-12-19  8:39     ` Carsten Dominik
2008-12-19 18:04       ` Samuel Wales
2008-12-19 22:32         ` Samuel Wales
2008-12-21 11:49           ` Carsten Dominik
2008-12-21 11:49     ` Carsten Dominik
2008-12-21 21:24       ` Samuel Wales
2008-12-22  8:30         ` Carsten Dominik [this message]
2008-12-23 19:40           ` Samuel Wales

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=A733F4DC-5CED-4258-9536-FC80932584C9@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@gmail.com \


* 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


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