From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: [the culprit]
Date: Tue, 26 Apr 2022 08:42:11 +0200 [thread overview]
Message-ID: <87h76gmjlo.fsf@mat.ucm.es> (raw)
In-Reply-To: 87h76gv5l8.fsf@localhost
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
>>> "IR" == Ihor Radchenko <yantar92@gmail.com> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
>>> But it does not help, org-set-property sets always a new property at the
>>> end of the property list.
>>
>>> Any idea what to do (besides touching the function itself)
>>
>>
>> It seems that the culprit is the function
>> org-entry-put
>> which always puts a new entry at the end of the property section.
> You are right, org-set-property adds the property to the end of property
> drawer. I do not think that its docstring suggests anything different.
> Do you want to propose a new feature request? I guess patches are welcome.
The question is what would be the best solution?
1. Change the behavior for org-entry-put
2. Or just for org-set-property.
If it is the first option, then maybe a variable should be added
org-set-property-at-line say, what could be t or nil.
Recently I use drawers that have a lot of properties, that I want a bit
organised, but if new properties are added always at the end, that
complicates things. What do others think (I don't have the feeling that
large drawers are very common).
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2022-04-26 6:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 8:13 org-set-property (at point)? Save-excursion seems not to work Uwe Brauer
2022-04-25 12:36 ` [the culprit] (was: org-set-property (at point)? Save-excursion seems not to work) Uwe Brauer
2022-04-26 4:20 ` Ihor Radchenko
2022-04-26 6:42 ` Uwe Brauer [this message]
2022-04-26 13:08 ` [the culprit] John Kitchin
2022-04-26 13:48 ` Ihor Radchenko
2022-04-27 13:12 ` Uwe Brauer
2022-04-27 18:49 ` Uwe Brauer
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=87h76gmjlo.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).