emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: probable caching bug?
Date: Thu, 05 Dec 2013 09:00:10 +0700	[thread overview]
Message-ID: <87pppcys45.fsf@ericabrahamsen.net> (raw)

While editing a plain list yesterday I noticed what I guess was a bug in
the caching mechanism.

The list item was wrapped to several lines, and I noticed that calling
C-e while on the last line gave me "wrong-type-argument
integer-or-marker-p nil". Trying to fill the item with M-q gave me
"user-error: An element cannot be parsed line 635".

I found that adding another item with M-RET allowed me to go back up to
the previous item and fill it successfully. Later on, though, the same
error cropped up with other items, and I wasn't always able to bang it
back into shape. I was right in the middle of something and didn't have
time for extensive debugging, but here's the text I was on, and the
traceback for the wrong type argument below that:

****** Selected Quotes

- Illness is a subtle negotiation [微调] between life and death. Like
  a never-ending course in philosophy, it has taught me some of the
  meaning of life, and of death.
- One can only save the drowning when oneself is on the shore.
- Night was falling. Carrying his large leather suitcase, Zhuang
  Zhidie arrived alone at the train station. After queuing for his ticket, <--- line 365

Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  org-element-item-parser(27819 ((27512 0 "- " nil nil nil 27681) (27681 0 "- " nil nil nil 27744) (27744 0 "- " nil nil nil 27819)) t)
  org-element--current-element(27819 element item ((27512 0 "- " nil nil nil 27681) (27681 0 "- " nil nil nil 27744) (27744 0 "- " nil nil nil 27819)))
  byte-code("BYTE CODE HERE" [element special-flag type pos org-element-use-cache org-element--cache (item table-row) (plain-list table) 0 org-element--cache-sync gethash eql objects org-element--current-element derived-mode-p org-mode nil org-element-cache-reset puthash :parent org-add-props plist-put plain-text (item plain-list) :structure :end get-text-property plist-get throw exit :contents-begin :contents-end (plain-list table) (center-block drawer dynamic-block inlinetask property-drawer quote-block special-block) (item plain-list) plain-list item property-drawer node-property table table-row org-element--cache-status data cached end struct parent value property elem-end ...] 6)
  org-element-at-point()
  org-end-of-line(nil)
  call-interactively(org-end-of-line nil nil)

             reply	other threads:[~2013-12-05  3:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05  2:00 Eric Abrahamsen [this message]
2013-12-05 15:47 ` probable caching bug? Nicolas Goaziou
2013-12-06  1:59   ` Eric Abrahamsen
2013-12-06 15:30     ` Nicolas Goaziou
2013-12-07  1:58       ` Eric Abrahamsen
2013-12-07  9:19         ` 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=87pppcys45.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).