From: Ihor Radchenko <firstname.lastname@example.org> To: Greg Sullivan <email@example.com> Cc: Hanno Perrey <firstname.lastname@example.org>, emacs-orgmode <email@example.com> Subject: Re: Inconsistent handling of multi-line properties Date: Sun, 20 Mar 2022 13:47:53 +0800 [thread overview] Message-ID: <87r16xdvjq.fsf@localhost> (raw) In-Reply-To: <CAMAo5zsh7Jag2e=5u0bigmF4o=Gw224Ap-BzZppxXuzzKcAjMA@mail.gmail.com> Greg Sullivan <firstname.lastname@example.org> writes: > I would really like the ability to use the ":myProperty+: " to create > multi-line properties for the org-export-taskjuggler exporter. > However, the mentioned patch is quite large and mostly focused on headline > caching, as far as I can tell. > @Ihor or @Hanno, Is there a patch just to get the :myProperty+: syntax to > work properly with org-element-property? That patch has been merged. However, the part about merging :myProperty+: into :myProperty: did not work as well as I thought initially. Now, all the instances of :myProperty+: do get merged and can be accessed via (org-element-property :MYPROPERTY+ element). However, they are not merged into :myProperty: because it would interfere with property inheritance. Merging everything into :MYPROPERTY is possible, but it might break third-party packages that do not expect element properties to be lists (currently, most export backends assume element properties to be strings). I am reluctant to work on this unless Nicolas displays a clear support of such change. An alternative could be modifying org-element-property or org-export-get-node-property to support multiline properties. Meanwhile, export backends might be changed to look into :PROPERTY+ in addition to :PROPERTY. For org-export-taskjuggler, you may implement this feature yourself. Note that org-export-taskjuggler is not a part of Org core. It is in org-contrib and currently not maintained. Best, Ihor
next prev parent reply other threads:[~2022-03-20 5:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-02 15:01 Hanno Perrey 2021-10-02 15:19 ` Ihor Radchenko 2022-02-28 20:09 ` Greg Sullivan 2022-03-20 5:47 ` Ihor Radchenko [this message] 2022-02-28 20:34 ` Kaushal Modi 2022-02-28 20:45 ` Kaushal Modi 2022-02-28 22:18 ` Greg Sullivan 2022-03-20 5:55 ` Ihor Radchenko
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=87r16xdvjq.fsf@localhost \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Inconsistent handling of multi-line properties' \ /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
Code repositories for project(s) associated with this 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).