From: Joseph Kern <jkern@semafour.net>
To: Brian Wood <bwood@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best practices? Multiple .org files?
Date: Thu, 1 Sep 2011 13:55:53 -0400 [thread overview]
Message-ID: <CALcYdLC1se98TNNRSDemANtgFEjLNKrQ46K-h2snDzQMdcN5nw@mail.gmail.com> (raw)
In-Reply-To: <4E5FC269.3000700@berkeley.edu>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On Thu, Sep 1, 2011 at 1:35 PM, Brian Wood <bwood@berkeley.edu> wrote:
> I've been using orgmode for 6 months and really like it. I started with on
> monolithic work.org file. I'm worried that at some point this file will
> get too big and bog down emacs. I'm not sure how big it would have to
> be...? To avoid that 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"?
>
> 2. Is there a way I can search for a string across all of my .org files
> from within orgmode?
>
Yes. Search view:
C-c a s
This is a special search that lets you select entries by matching a
substring or specific words using a boolean logic
http://orgmode.org/guide/Search-view.html
>
> --
> Brian Wood
> Applications Programmer
> UC Berkeley IST Application Services
>
>
>
[-- Attachment #2: Type: text/html, Size: 2836 bytes --]
next prev parent reply other threads:[~2011-09-01 17:55 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALcYdLC1se98TNNRSDemANtgFEjLNKrQ46K-h2snDzQMdcN5nw@mail.gmail.com \
--to=jkern@semafour.net \
--cc=bwood@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.