From: Carsten Dominik <dominik@science.uva.nl>
To: Peter Westlake <peter.westlake@pobox.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problems with refiling
Date: Wed, 18 Feb 2009 15:57:10 +0100 [thread overview]
Message-ID: <13C20A36-572B-4D06-BFA2-64D141634FCA@uva.nl> (raw)
In-Reply-To: <1234955845.19199.1301040675@webmail.messagingengine.com>
On Feb 18, 2009, at 12:17 PM, Peter Westlake wrote:
>
> On Tue, 17 Feb 2009 22:32:28 +0100, "Carsten Dominik"
> <dominik@science.uva.nl> said:
>> Hi Peter,
>>
>> the whole purpose of completing in steps is that you see the
>> level 2 headlines only after you have selected the level 1 headline.
>>
>> Am I missing something here?
>
> Yes: the level 2 headlines never appear. Instead, the entry is refiled
> to the level 1, unless files are listed, in which case it doesn't move
> at all. I must be missing out on some secret keystroke to continue the
> step-by-step process, I guess.
Like pressing a few characters and pressing TAB? Maybe you are
using the mouse to select top level headlines? I never use
the mouse for completion, and this might well be the problem.
When you click with the mouse, you are telling the program that you are
done completing.
Are you, by any change, using `org-completion-use-ido' as well?
I believe yesterday I forces off ido for the case of stepwise path
completion.
There was a bug fix only yesterday, I think, about this.
- Carste
>
>
> Regards,
>
> Peter.
>
>> - Carsten
>>
>> On Feb 17, 2009, at 6:19 PM, Peter Westlake wrote:
>>
>>> If I switch org-outline-path-complete-in-steps on, refiling breaks.
>>> How
>>> it breaks depends on org-refile-use-outline-path:
>>>
>>> Yes: Top level headlines are available, nothing else.
>>> Not: Same.
>>> Start with file: only the files are listed. The headline doesn't
>>> move.
>>>
>>> In the completion window, entries with sub-headlines appear in blue,
>>> but I can't find a way to get to the sub-headlines. What am I
>>> missing?
>>>
>>> org-refile-targets is
>>> ((org-agenda-files :maxlevel . 3)
>>> (nil :maxlevel . 3))
>>>
>>> So I would expect to see headlines down to level 3.
>>>
>>> Peter.
>>>
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Remember: use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>
next prev parent reply other threads:[~2009-02-18 14:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 17:19 Problems with refiling Peter Westlake
2009-02-17 21:32 ` Carsten Dominik
2009-02-18 11:17 ` Peter Westlake
2009-02-18 14:57 ` Carsten Dominik [this message]
2009-02-18 16:55 ` Peter Westlake
2009-02-19 15:29 ` Carsten Dominik
2009-02-19 17:32 ` Peter Westlake
2009-02-20 10:05 ` Carsten Dominik
2009-02-20 0:02 ` Netbook display of the org-mode site David Thole
2009-02-20 0:30 ` Samuel Wales
2009-02-20 7:08 ` Sebastian Rose
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=13C20A36-572B-4D06-BFA2-64D141634FCA@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=peter.westlake@pobox.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).