emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Feature request: "task table" (similar to clock table)
Date: Tue, 03 Jan 2023 18:29:17 +0000	[thread overview]
Message-ID: <87o7rfii9u.fsf@localhost> (raw)
In-Reply-To: <877cy3a478.fsf@mbork.pl>

Marcin Borkowski <mbork@mbork.pl> writes:

> I see.  I think I'll go another route then - in fact, I already started,
> see https://mbork.pl/2023-01-02_Computing_Org_mode_TODO_stats :-)

That will also work.

But why `plist-get' + `org-element-at-point-no-context'?

You can instead use `org-element-property' + `org-element-at-point'.
`org-element-property' will be resilient against internal AST
representation changes and `org-element-at-point' will make use of
caching.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2023-01-03 18:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26  7:50 Feature request: "task table" (similar to clock table) Marcin Borkowski
2022-12-26  8:05 ` Ihor Radchenko
2022-12-26  8:12   ` Marcin Borkowski
2022-12-26  8:26     ` Ihor Radchenko
2022-12-27  7:13       ` Marcin Borkowski
2022-12-27  7:48         ` Ihor Radchenko
2023-01-03 18:00           ` Marcin Borkowski
2023-01-03 18:29             ` Ihor Radchenko [this message]
2023-01-04  5:48               ` Marcin Borkowski
2023-01-23 20:48               ` Marcin Borkowski
2023-01-24  9:59                 ` Ihor Radchenko
2023-01-24 20:09                   ` Marcin Borkowski
2023-01-25  2:37                     ` Max Nikulin
2023-01-25 19:53                       ` Marcin Borkowski

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=87o7rfii9u.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    /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).