emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Scott Jaderholm <jaderholm@gmail.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: 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 04:06:56 -0400	[thread overview]
Message-ID: <CAA9PRe_5xNUzsL9LAAPq390oV_2LtvFsicsQS+zCMn6Wrd5Tsw@mail.gmail.com> (raw)
In-Reply-To: <877h48kqgp.fsf@thinkpad.tsdh.de>

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

Btw I get that behavior in emacs 23.1 too
Scott


On Fri, Oct 14, 2011 at 3:00 AM, Tassilo Horn <tassilo@member.fsf.org>wrote:

> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
>
> Hi Marcelo,
>
> > 4328, exactly the same amount of lines I have in the file.
>
> Didn't you say that you have 4000 *k* lines?
>
> Anyway, as Scott mentiones, in emacs 24 the linum packages seems to be
> more clever and only creates overlays for the visible area of a buffer.
> For example, when opening a file with 1000 lines and enabling
> linum-mode, I only have 35 overlays, because only 35 lines are visible
> at a time.
>
> Bye,
> Tassilo
>
> > On Thu, Oct 13, 2011 at 2:07 AM, Tassilo Horn <tassilo@member.fsf.org
> >wrote:
> >
> >> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> >>
> >> > Wow.. this worked Torsten. Thank you. I wonder why this happens...
> >>
> >> linum-mode works with overlays to embed the numbers at the beginnig of
> >> lines.  Overlays are very flexible but not too efficient, you don't want
> >> to have too many of them.  Looking at linum.el, it seems it already does
> >> pooling of overlays in order not to create one overlay for any line, but
> >> I'm not sure.  Could you please do
> >>
> >>  M-: (length linum-overlays) RET
> >>
> >> in that large org file with linum-mode enabled and say what it returns
> >> to satisfy my curiosity?
> >>
> >> Bye,
> >> Tassilo
> >>
> >>
> >>
>
>

[-- Attachment #2: Type: text/html, Size: 2202 bytes --]

  reply	other threads:[~2011-10-14  8:07 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
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 [this message]
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:
  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=CAA9PRe_5xNUzsL9LAAPq390oV_2LtvFsicsQS+zCMn6Wrd5Tsw@mail.gmail.com \
    --to=jaderholm@gmail.com \
    --cc=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tassilo@member.fsf.org \
    --subject='Re: Ways to make org feasible for huge files' \
    /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).