emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Cecil Westerhof <cldwesterhof@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: API problem
Date: Wed, 22 Jan 2014 21:40:36 +0100	[thread overview]
Message-ID: <87r47zvjgb.fsf@gmail.com> (raw)
In-Reply-To: <CAG-LmmAZJmRKc7QQFHn9cX+W-9sdtnncS_eZ_fHAsb-1W75Fig@mail.gmail.com> (Cecil Westerhof's message of "Wed, 22 Jan 2014 21:28:11 +0100")

Cecil Westerhof <cldwesterhof@gmail.com> writes:

> I have an org-file wth the folowing:
> - [ ] A (setq struct (org-list-struct))
> - [-] B (org-list-get-checkbox 41 struct)
> - [ ] C (org-list-set-checkbox 41 struct "[X]")
> - [ ] D (org-list-get-checkbox 41 struct)
> - [ ] E (org-list-write-struct struct (org-list-parents-alist struct))
> In A I fill the struct.
> B displays "[-]"
> C displays "[X]"
> D displays "[X]", so the struct is correctly updated.
> E gives: #<marker in no buffer>
> What is going wrong here?

See `org-list-write-struct' docstring. Basically, STRUCT doesn't match
real structure anymore since step C. You need to provide the original
structure as a third argument so `org-list-write-struct' can modify
buffer by set difference.

  (let* ((struct (org-list-struct))
         (old (copy-tree struct)))
    (org-list-set-checkbox (line-beginning-position) struct "[X]")
    (org-list-write-struct struct (org-list-parents-alist struct) old))


Nicolas Goaziou

  reply	other threads:[~2014-01-22 20:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 16:37 API problem Cecil Westerhof
2014-01-22 17:03 ` Nicolas Goaziou
     [not found]   ` <CAG-LmmApJwvTvTYZ3cFjb_rLkiX9B_JP3FzTX-D_kW3H1=D6pA@mail.gmail.com>
2014-01-22 20:24     ` Fwd: " Cecil Westerhof
2014-01-22 20:28       ` Cecil Westerhof
2014-01-22 20:40         ` Nicolas Goaziou [this message]
2014-01-22 21:57           ` Cecil Westerhof
2014-01-22 22:23             ` Nicolas Goaziou
2014-01-22 23:52           ` Cecil Westerhof

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=87r47zvjgb.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=cldwesterhof@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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