Re: [O] Ways to make org feasible for huge files

[brian powell]

* Maybe EMACS  "narrowing" could be used:
http://www.gnu.org/s/libtool/manual/emacs/Narrowing.html
...
Narrowing can make it easier to concentrate on a single subroutine or
paragraph by eliminating clutter. It can also be used to limit the
range of operation of a replace command or repeating keyboard macro.
...
C-x n n
Narrow down to between point and mark (narrow-to-region).
C-x n w
Widen to make the entire buffer accessible again (widen).
C-x n p
Narrow down to the current page (narrow-to-page).
C-x n d
Narrow down to the current defun (narrow-to-defun).

** I mean: Maybe an OrgMode user could do narrow-to-region (and then
just "render" on the new smaller region) and/or an implementation
something like "org-narrow-to-region" could be coded.

*** Just an idea--your mileage may vary--it may not work at all--I
hope you try it out and tell how it works for you.

* I ran into similar problems: I made the file into 2 separate
files--one very large and the other very small that I render a
lot--when it gets big, I just prune out older and less important now
(backburner) subjects, paste them at the bottom of the small file and
then cut and paste the less important "*" sections into the big file.
** Works great, its really the best way to do it--for backing up and
encrypting reasons and hard drive space reasons etc.
** Could call them blahfile_now.org and blahfile_later.org (for the
small and large files respectively).
*** Since OrgMode files are plain text files, this works great.

On Wed, Oct 12, 2011 at 8:54 PM, Marcelo de Moraes Serpa
<address@hidden> wrote:
> Hi list,
>
> I love org and I think there's nothing like it out there, but I'm
> considering using Evernote for reference notes, because my reference.org
> file has grown too big (4234k + lines). This makes the rendering of the file
> way too slow, and 2 times out of 10 emacs crashes because of that.