emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>,
	No Wayman <iarchivedmywholelife@gmail.com>,
	Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [RFC] DOCT: Declarative Org Capture Templates (easier template syntax)
Date: Tue, 29 Mar 2022 10:19:31 -0400	[thread overview]
Message-ID: <CAN_Dec_iaCJ848PViruBcq+xWJE91=rA35+UJ0vTdDtpPQAJdQ@mail.gmail.com> (raw)
In-Reply-To: <87k0chyv2y.fsf@localhost>

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

On Sat, Mar 26, 2022 at 4:31 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> No Wayman <iarchivedmywholelife@gmail.com> writes:
> > I'm open to bringing doct's features into Org mode, but I'd prefer
> > it not to be spread out over another two years.
> Proper integration of doct into org-capture.el would indeed be ideal. I
> am happy that you are ok with such option.
> Practically, we can do it step-by-step in separate patches:
> 1. Introduce alist format for org-capture-templates. No new
>    functionality yet, just change the existing supported template
>    options to :keyword value pairs. Also, make sure that we keep
>    backwards compatibility.
> 2. Extend the alist with new options, like ${keyword} expansion, hooks,
>    contexts, children, etc Maybe in a sequence of patches.
> 3. Provide validation of capture templates.
> Best,
> Ihor

I'll just say that I would be an enthusiastic adopter of the new syntax
(just one data point). I agree wholeheartedly that named properties in
plists are much easier to remember and adjust than positional arguments,
especially when there are lots of the latter.   So, I hope this move

[-- Attachment #2: Type: text/html, Size: 1678 bytes --]

  parent reply	other threads:[~2022-03-29 14:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 17:30 [RFC] DOCT: Declarative Org Capture Templates No Wayman
2020-04-24 10:01 ` Nicolas Goaziou
2020-04-24 18:01   ` No Wayman
2022-03-20 10:19     ` [RFC] DOCT: Declarative Org Capture Templates (easier template syntax) Ihor Radchenko
2022-03-20 13:17       ` Nicolas Goaziou
2022-03-21  9:14         ` Ihor Radchenko
2022-03-23 16:31           ` Nicolas Goaziou
2022-03-23 21:28             ` Tim Cross
2022-03-24  0:39             ` No Wayman
2022-03-26  8:30               ` Ihor Radchenko
2022-03-27 14:46                 ` Ihor Radchenko
2022-03-29 14:19                 ` Matt Price [this message]
2022-03-20 15:56       ` Mark Barton
2022-03-21  8:51         ` Ihor Radchenko
2022-03-23 14:32       ` João Pedro de Amorim Paula
2022-03-24 18:43       ` physiculus

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='CAN_Dec_iaCJ848PViruBcq+xWJE91=rA35+UJ0vTdDtpPQAJdQ@mail.gmail.com' \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=iarchivedmywholelife@gmail.com \
    --cc=mail@nicolasgoaziou.fr \
    --cc=yantar92@gmail.com \


* 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).