emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: element-debug-mode breaks capture
Date: Wed, 19 Aug 2015 11:39:42 +0200	[thread overview]
Message-ID: <87lhd7aamd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87r3n08uw8.fsf@gnu.org> (Bastien's message of "Tue, 18 Aug 2015 17:43:19 +0200")

Hello,

Bastien <bzg@gnu.org> writes:

> I also had a lot of these recently.

I posted some tricks on the ML to help debug the problem. Also, a single
cache corruption can lead to many error reports (basically whenever
a command relying on `org-element-at-point' is used).

> I'm now turning org-element-use-cache off and I don't see real issue
> when not using it.
>
> Nicolas, what's the real benefit of using the cache?  Is it with
> large files?  With frequent updates of the structure?  What actions
> are the most impacted by not using the cache?

It makes `org-element-context'/`org-element-at-point' very fast in
almost every situation. This is of course the most noticeable when
editing large sections.

However, once remaining glitches in the cache are fixed, I expect to
make fontification use it. So, turning cache off in the long run doesn't
help moving forward, though it may be convenient in some unfortunate
situations.


Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2015-08-19  9:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-16 20:52 element-debug-mode breaks capture Samuel Wales
2015-08-18 15:43 ` Bastien
2015-08-19  9:39   ` Nicolas Goaziou [this message]
2015-08-19 10:27     ` Bastien
2015-08-19 10:34       ` Nicolas Goaziou
2015-08-19 10:55         ` Bastien
2015-08-19 12:14           ` Eric S Fraga
2015-08-19 13:04             ` Bastien
2015-08-19 13:43               ` Nicolas Goaziou

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=87lhd7aamd.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bzg@gnu.org \
    --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 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).