From: Matthew Lundin <email@example.com> To: Carsten Dominik <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Refile as top-level headlines? Date: Sun, 18 Jan 2009 10:31:13 -0600 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <C5BBAF90-469F-4064-A036-ACE2718B189E@uva.nl> (Carsten Dominik's message of "Sat\, 17 Jan 2009 13\:37\:53 +0100") Carsten Dominik <email@example.com> writes: > On Jan 14, 2009, at 4:49 PM, Matthew Lundin wrote: > >> >> Hi everyone, >> >> I have a lot of org-files and use org-refile all the time as part of >> my normal workflow. My basic approach is to remember things to an >> inbox.org file and then to process the inbox GTD-style. >> >> One thing I'm having a hard time figuring out is how to refile headers >> as top level headlines in a target file. I've customized org-refile >> with the following settings: >> >> ,---- >> | (setq org-refile-use-outline-path 'file) >> | (setq org-refile-targets '((org-agenda-files :maxlevel . 1) >> | (nil :maxlevel . 3))) >> `---- >> >> (Note: the second setting in org-refile-targets gives me additional, >> deeper targets in whatever file I'm visiting.) >> >> What I'd like to see is for maxlevel to include the possibility of >> filing an item as a top-level headline (at the bottom of the file). > > Hmmm, how would you like the interface to work? Just have an entry > in the list that is only the file name? And if it is only a single > file, > just replying with the empty string? 1. First idea: Perhaps this option could be activated only when: (setq org-refile-use-outline-path 'file) Currently with the above setting and refile targets with a maxlevel of 2, completion with refile offers the following targets: computer.org/headline/ (computer.org) vs. computer.org/headline/subheading/ (computer.org) To file under the first target, one can hit space after completing headline. Perhaps there could also be an option for hitting space after the first completion, i.e., after computer.org. computer.org/ (computer.org) 2. Second idea: Another possibility would be as you suggest: to offer the file name independently as one of the targets. And if it's only one file, perhaps the file name could still be offered as a target the sake of clarity. This would then work regardless of the setting of org-refile-use-outline-path. I realize not everyone would want this behavior. Maybe one would need to set it explicitly either by (1) setting level to 0 for org-refile-targets or (2) making maxlevel a negative number (i.e., if positive then don't offer level 0 targets; if negative offer level 0 targets). Just an idea.... I'm sure your ideas about this will be much better! :-) Thanks for considering this. Matt
next prev parent reply other threads:[~2009-01-18 16:31 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-14 15:49 Matthew Lundin 2009-01-17 12:37 ` Carsten Dominik 2009-01-18 16:31 ` Matthew Lundin [this message] 2009-04-04 3:04 ` Carsten Dominik
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Refile as top-level headlines?' \ /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
Code repositories for project(s) associated with this 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).