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: getting org-goto to work with ido
Date: Tue, 25 Nov 2008 23:39:57 +0100	[thread overview]
Message-ID: <D703946C-0738-4341-A443-116C66CE305B@uva.nl> (raw)
In-Reply-To: <20524da70811251207o3eb6eb38gecc0751772919430@mail.gmail.com>

Hi Samuel,

On Nov 25, 2008, at 9:07 PM, Samuel Wales wrote:

> On Mon, Nov 24, 2008 at 02:59, Carsten Dominik  
> <dominik@science.uva.nl> wrote:
>> (setq org-outline-path-complete-in-steps nil)
>>
>> Then targets for org-goto will still be identified by their entire
>> path, in this way removing disambiguates,  but you can then use
>> single-step completion to match the entire path, using ido if you  
>> wish.
>
> Kind of like uniquify?



Well, not quite.  Uniquify does only prepend the path
if necessary - what I have implemented always has the
complete path.  I agree that a uniquify approach might
be nice as well.

> I don't have git, but if this is what I think you mean, then I had the
> same idea, except for a different reason.
>
> Let's say you have housing/environment/filters and
> food/coffee/filters.  And also 10 more.  You type "fil" and there are
> 15 candidates.  To select the coffee one, you type c-spc then "cof".
> In other words, I wanted to do the headline first then the path.

I just tried (I did not know about C-SPC in ido, great feature),
and this works just fine.

However, my standard way to work is to just type a substring
and then use C-s to cycle through the possibilities.  But I
might make more use of C-SPC, like the idea.

> An improvement would be to put the path *after* the headline (in
> reverse order like filters\coffee\food; see uniquify for code and to
> make the syntax consistent).  Then c-spc would not be necessary.  You
> would type "filcof".  If that is not enough to disambiguate, then
> "fo".
> No backtracking necessary.
>
> Then the minibuffer can show tersely if desired.  filters\coffee,
> filters\environment.  Or just enough to be unique.


It does show the full path right now, which can be long, of course.

> If that's what you mean, then we have a winner.

I do like it a lot, but I think I should make a more
terse list with uniquify.  Maybe there is some emacs/uniquify code I  
can reuse....

- Carsten

>
>
> But is it fast in CPU time to gather the headlines this way?
> :maxlevel isn't necessary?
>
>> Wow, this is *really* fast.
>
> Yeah.
>
>> Maybe I should start by setting the default for org-goto-interface to
>> outline-path-completion.
>> Any thoughts about such a change?
>
> Maybe depends on CPU time on large files and what you set the ido
> default to.  Of course, ido has limits you can set also.  I presume
> emacs and xemacs both have ido.
>
> I would use it.
>
> -- 
> Myalgic encephalomyelitis denialists are knowingly causing further
> suffering and death by opposing biomedical research on this
> fast-spreading serious disease.  Do you care about the world?
> http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm

      reply	other threads:[~2008-11-25 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 21:13 getting org-goto to work with ido Samuel Wales
2008-11-24  9:59 ` Carsten Dominik
2008-11-25 20:07   ` Samuel Wales
2008-11-25 22:39     ` Carsten Dominik [this message]

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.orgmode.org/

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

  git send-email \
    --in-reply-to=D703946C-0738-4341-A443-116C66CE305B@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=samologist@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).