emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org, Gregor Kappler <g.kappler@gmx.net>
Subject: Re: adapted org-flag-drawer to hide newlines of consecutive drawers to save lines
Date: Wed, 13 Nov 2013 12:24:51 +0100	[thread overview]
Message-ID: <87mwl8ee7w.fsf@gmail.com> (raw)
In-Reply-To: <87fvr03cq3.fsf@bzg.ath.cx> (Bastien's message of "Wed, 13 Nov 2013 09:52:36 +0100")

Bastien <bzg@gnu.org> writes:

> Is the cache activated by default?

Yes, it is.

There's an emergency variable, `org-element-use-cache' to disable it,
but it should be used for debugging purpose only. From the user point of
view, if the cache appears to be corrupted due to a bug, it may be
simpler to call `org-element-cache-reset'.

> If so, does it come with some inconveniency?

As every cache, you pay the full price the first time you fill it. For
example, there may be a small overhead when opening an Org file.

Most editing operations only remove the current element from the cache,
but some of them (mostly operations on blocks and drawers boundaries)
delete larger parts of it. As such, these are more expensive than the
average.

> If not, should we simply activate it all the time?

We really should.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-11-13 11:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 15:47 adapted org-flag-drawer to hide newlines of consecutive drawers to save lines Gregor Kappler
2013-11-12 21:46 ` Bastien
2013-11-13  8:20   ` Nicolas Goaziou
2013-11-13  8:52     ` Bastien
2013-11-13 11:24       ` Nicolas Goaziou [this message]
2013-11-13 11:43         ` Bastien
2013-11-14 17:43           ` Nicolas Goaziou
2013-11-14 22:55             ` Bastien
2013-11-15 16:56               ` Nicolas Goaziou
2013-11-15 19:30                 ` Bastien

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=87mwl8ee7w.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=g.kappler@gmx.net \
    /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).