emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [the culprit]
Date: Tue, 26 Apr 2022 09:08:47 -0400	[thread overview]
Message-ID: <CAJ51ETo+C2GOFT-DqqgzbHQk1FAOzgV2ZuNqNbav0mnFcrsONg@mail.gmail.com> (raw)
In-Reply-To: <87h76gmjlo.fsf@mat.ucm.es>

[-- Attachment #1: Type: text/plain, Size: 2312 bytes --]

This seems like something that could (should?) go in a personal config, as
a custom function, or advice.

You could, for example do something like this (lightly tested)

#+BEGIN_SRC emacs-lisp
(defun my-put (property value here)
  (interactive (list nil nil current-prefix-arg))
  (if (null here)
      (org-set-property property value)
    (let* ((property (or property (org-read-property-name)))
  (value (or value (org-read-property-value property))))
(search-forward ":")
(insert (format ":%s: %s\n" property value))))))

if you call it as M-x my-put, it just uses org-set-property.

If you call it as C-u M-x my-put, it inserts the property before the point.
It does not check you are in a property drawer, which could be a good idea.


Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213

On Tue, Apr 26, 2022 at 2:43 AM Uwe Brauer <oub@mat.ucm.es> wrote:

> >>> "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: Type: text/html, Size: 3403 bytes --]

  reply	other threads:[~2022-04-26 13:15 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     ` [the culprit] Uwe Brauer
2022-04-26 13:08       ` John Kitchin [this message]
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:

  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=CAJ51ETo+C2GOFT-DqqgzbHQk1FAOzgV2ZuNqNbav0mnFcrsONg@mail.gmail.com \
    --to=jkitchin@andrew.cmu.edu \
    --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).