From: Tyler Grinn <tylergrinn@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Concatenate properties
Date: Mon, 09 May 2022 16:18:11 -0400 [thread overview]
Message-ID: <87mtfq8np8.fsf@gmail.com> (raw)
In-Reply-To: <877d6wqdxs.fsf@localhost> (Ihor Radchenko's message of "Sun, 08 May 2022 22:47:11 +0800")
Ihor Radchenko <yantar92@gmail.com> writes:
> Tyler Grinn <tylergrinn@gmail.com> writes:
>
>>
>> Could you provide an example of what the value of that variable would be
>> if, for instance, I wanted PROP_A and PROP_B to be joined with a single
>> space and PROP_C and PROP_D to be concatenated? Or better yet, have the
>> default be to join with a single space for any property and have only
>> PROP_C and PROP_D concatenated?
>
> Say,
>
> '(("PROP_[CD]" . ""))
>
> or
>
> '(("PROP_[AB]" . "/") ("PROP_[CD]" . "") (".+" . "∿"))
>
> Best,
> Ihor
I'm not sure forcing regular expressions for all use cases is ideal. Is
there a way to allow the option (I'm calling it org-property-separators)
to allow either regular expressions or exact matches, like
org-use-property-inheritance does?
Other than that I'm mostly ready to send in my first patch. Should I
attach it in this thread or start a new one?
Best,
Tyler
next prev parent reply other threads:[~2022-05-09 20:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 22:37 Concatenate properties Tyler Grinn
2022-05-05 22:56 ` John Kitchin
2022-05-06 15:40 ` Tyler Grinn
2022-05-07 5:33 ` Ihor Radchenko
2022-05-07 11:44 ` John Kitchin
2022-05-07 12:29 ` Tyler Grinn
2022-05-08 12:21 ` Ihor Radchenko
2022-05-08 14:14 ` Tyler Grinn
2022-05-08 14:47 ` Ihor Radchenko
2022-05-09 20:18 ` Tyler Grinn [this message]
2022-05-11 11:51 ` Ihor Radchenko
2022-05-11 17:47 ` [PATCH] " Tyler Grinn
2022-05-12 9:59 ` Ihor Radchenko
2022-05-12 23:27 ` Tyler Grinn
2022-05-13 12:21 ` Ihor Radchenko
2022-05-14 2:11 ` Tyler Grinn
2022-05-20 8:04 ` Ihor Radchenko
2022-05-07 13:20 ` John Kitchin
2022-05-07 14:09 ` Tyler Grinn
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=87mtfq8np8.fsf@gmail.com \
--to=tylergrinn@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).