From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: org-set-properties for various (all) headings
Date: Wed, 20 Jul 2022 10:05:40 +0200 [thread overview]
Message-ID: <877d4843aj.fsf@mat.ucm.es> (raw)
In-Reply-To: 87pmi02q8a.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]
>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>> Two comments though
>>
>> 1. It works, if the source block is at the beginning of the file 😉
>>
>> 2. I confess I don't understand anymore the use of `(let ((el (org-element-at-point)))':
>>
>> a. In your first version you used the defined «el», but know you
>> don't, hm just saying.
> That's because the first version used the actual headline title as a
> value of the property. That values had to be acquired somehow.
> org-element API was used.
I expressed myself rather badly
1. First code
(defun test/set-property-at-heading ()
"Function to be called at the beginning of an Org heading."
(interactive)
(let ((el (org-element-at-point)))
(org-set-property "foo" (org-element-property :title el))))
^el is used
(org-map-entries #'test/set-property-at-heading)
2. Second code
(defun test/set-property-at-heading ()
"Function to be called at the beginning of an Org heading."
(interactive)
(let ((el (org-element-at-point)))
^el is defined but not used.
(org-set-property "New" "[ ]")))
(org-map-entries #'test/set-property-at-heading)
>> In any case thanks again for this very valuable advice. I suggest to
>> include it somehow in the documentation, since I believe that other
>> users have encountered similar situations.
> A.11 Using the Mapping API
> A.10 Using the Property API
Is this a reference to the manual?
🙄
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-07-20 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 8:14 org-set-properties for various (all) headings Uwe Brauer
2022-07-19 10:56 ` Kaushal Modi
2022-07-19 14:53 ` Uwe Brauer
2022-07-19 16:30 ` Kaushal Modi
2022-07-19 16:56 ` Uwe Brauer
2022-07-19 18:07 ` Kaushal Modi
2022-07-20 5:31 ` Uwe Brauer
2022-07-20 7:33 ` Ihor Radchenko
2022-07-20 8:05 ` Uwe Brauer [this message]
2022-07-20 13:00 ` Kaushal Modi
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=877d4843aj.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).