emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jude DaShiell <jdashiel@shellworld.net>
To: brian powell <briangpowellms@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	Marcelo de Moraes Serpa <celoserpa@gmail.com>
Subject: Re: Ways to make org feasible for huge files
Date: Fri, 14 Oct 2011 05:54:13 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.00.1110140552510.8669@freire1.furyyjbeyq.arg> (raw)
In-Reply-To: <CAFm0skFnvyfdG86=3JZXKtvmwhFSpiQQ2_a54eUG2h6-aKw+8Q@mail.gmail.com>

Why not working-file and archive-file?  Archive-file would be the big 
file and working-file would be the small file in that scheme.

On Wed, 12 Oct 2011, brian powell wrote:

> * 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
> <celoserpa@gmail.com> 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.

Jude <jdashiel@shellworld.net>
If I got a nickel for every message I've already sent supporting Microsoft
Windows and its applications I'd have enough to retire on comfortably no
matter what the stock market did.

  parent reply	other threads:[~2011-10-14  9:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  0:54 Marcelo de Moraes Serpa
2011-10-13  1:34 ` brian powell
2011-10-13  1:47   ` Thomas S. Dye
2011-10-14  9:54   ` Jude DaShiell [this message]
2011-10-13  2:44 ` Torsten Wagner
2011-10-13  2:52   ` Marcelo de Moraes Serpa
2011-10-13  7:07     ` Tassilo Horn
2011-10-14  1:23       ` Marcelo de Moraes Serpa
2011-10-14  4:51         ` Scott Jaderholm
2011-10-14  7:00         ` Tassilo Horn
2011-10-14  8:06           ` Scott Jaderholm
2011-10-14  8:52             ` Jude DaShiell
2011-10-13 12:39 ` GNU Emacs crashing on large Orgmode files (was: Ways to make org feasible for huge files) Karl Voit
2011-10-13 14:56   ` GNU Emacs crashing on large Orgmode files Martyn Jago
2011-10-14  6:14   ` Karl Voit

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:

  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=alpine.BSF.2.00.1110140552510.8669@freire1.furyyjbeyq.arg \
    --to=jdashiel@shellworld.net \
    --cc=briangpowellms@gmail.com \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Ways to make org feasible for huge files' \


* 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:


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).