From: John Hendy <email@example.com> To: Skip Collins <firstname.lastname@example.org> Cc: emacs-org list <email@example.com> Subject: Re: refile and link Date: Wed, 1 Feb 2012 09:25:44 -0600 [thread overview] Message-ID: <CA+M2ft8U0NDSK=9m1mg4e_EzSqtNGMZY8k=Ph12GbDJC56EFYA@mail.gmail.com> (raw) In-Reply-To: <CABUh-76AhD3j9azDShmC3AzqLGyK+DJQ+Jcesia4KeZUS=yHkw@mail.gmail.com> On Tue, Jan 31, 2012 at 12:49 PM, Skip Collins <firstname.lastname@example.org> wrote: > I would like to have a quick way to refile subtrees in another file > while creating a link to the new location. In my use case, I keep a > comprehensive list of projects in Projects.org. Each top level > headline is the title of a project. Some projects details (TODOs, > notes, etc.) may be included under the headline. A project may grow to > the point that I want to manage it within a separate org file. In this > case it would be fantastic to have a quick refile command that leaves > behind the original headline and a link to the new location. Does this > make sense? Maybe I should be using agendas to accomplish what I want. > But keeping a canonical list of projects in a single file seems like > the right thing to do. > Makes sense and seems really neat. This could even be used to fulfill a suggested organization structure from the orgmode FAQ: ,----- (http://orgmode.org/worg/org-faq.html#how-to-organize-org-mode-files):----- | Should I use one big org file or multiple files? | [...] | Here are a few ideas for organizing org-mode files: | [...] | - A wiki of hyperlinked files that grows and adapts to meet your needs. `----- I hope you get a solution! John > -- > skip collins >
next prev parent reply other threads:[~2012-02-01 15:25 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-31 18:49 Skip Collins 2012-02-01 15:25 ` John Hendy [this message] 2012-02-01 15:54 ` Skip Collins 2012-02-01 17:58 ` John Hendy
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='CA+M2ft8U0NDSK=9m1mg4e_EzSqtNGMZY8k=Ph12GbDJC56EFYA@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: refile and link' \ /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).