From: Joseph Kern <jkern@semafour.net>
To: mail@christianmoe.com
Cc: emacs-orgmode@gnu.org, Brian Wood <bwood@berkeley.edu>
Subject: Re: Best practices? Multiple .org files?
Date: Fri, 2 Sep 2011 08:37:54 -0400 [thread overview]
Message-ID: <CALcYdLAG0VTzDYZoqGE=o-vUS-2eCX9zoVS9YOQKdYeg5o3Rtg@mail.gmail.com> (raw)
In-Reply-To: <4E60B155.7060708@christianmoe.com>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Is there a way to display the contents of the file in-line?
On Fri, Sep 2, 2011 at 6:35 AM, Christian Moe <mail@christianmoe.com> wrote:
> On 9/1/11 7:35 PM, Brian Wood wrote:
>
>> (...) I'm thinking that I should break up
>>
>> this file into multiple .org files in a directory. If I do that:
>>
>> 1. I would like to still see the same top-level tree that I see now
>> when I shift-Tab e.g:
>>
>> * Admin
>> * Drupal
>> * MacOS
>> * Linux
>> * Time Reports
>>
>> So if I create drupal.org that contains the contents of "* Drupal",
>> and I remove "* Drupal" from work.org, is there a way to still see my
>> top level tree including "Drupal"?
>>
>
> I keep some top-level headings in my central `my.org' file after I've
> hived off the contents to other org files, just to have a convenient link to
> the file and save myself having to remember how I named it.
>
> So I'd do something like:
>
> * Admin
> * [[file:./drupal.org][Drupal]]
> * MacOS
> * Linux
> * Time Reports
>
> Don't forget to add the new files to your agenda files, the agenda view
> being the chief way of pulling together all your tasks.
>
> Yours,
> Christian
>
>
[-- Attachment #2: Type: text/html, Size: 1881 bytes --]
next prev parent reply other threads:[~2011-09-02 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 17:35 Best practices? Multiple .org files? Brian Wood
2011-09-01 17:55 ` Joseph Kern
2011-09-01 18:38 ` Brian Wood
2011-09-01 21:01 ` Darlan Cavalcante Moreira
2011-09-01 22:47 ` suvayu ali
2011-09-02 10:35 ` Christian Moe
2011-09-02 12:37 ` Joseph Kern [this message]
2011-09-02 12:55 ` Eric S Fraga
2011-09-02 16:36 ` Brian Wood
2011-09-02 18:28 ` Eric S Fraga
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='CALcYdLAG0VTzDYZoqGE=o-vUS-2eCX9zoVS9YOQKdYeg5o3Rtg@mail.gmail.com' \
--to=jkern@semafour.net \
--cc=bwood@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.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).