From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: org-capture-templates constructed from three distinct functions
Date: Sat, 12 Dec 2020 03:17:50 +0100 [thread overview]
Message-ID: <trinity-949fcf58-8338-469c-a935-9401854ef87a-1607739470495@3c-app-mailcom-bs06> (raw)
In-Reply-To: <87r1nvg486.fsf@zoho.eu>
> Sent: Saturday, December 12, 2020 at 3:14 AM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: org-capture-templates constructed from three distinct functions
>
> Christopher Dimech wrote:
>
> > This is how I interpreted your list comment
>
> OK, well, that was just playing with syntax and having fun at
> your comment ("backquote construct), but be my guest...
I wrote bullocks then.
> > (setq captr-templ-tdr
> > `(,@(list
> > '("t" "Tdr Document") ; backquote construct
> > '("t1" "Tdr: Ch01 Oceanic Microseismology" entry
> > (file+headline "~/02histr/tdr/01ch.rcl.org" "Tdr Document")
> > ,(concat "* Oceanic Microseismology\n" ; special marker
> > " %^{Select |Augment:|Include:|Clarify:|Organise:} %?\n"
> > " Scheduled: %^T\n Entered: %T\n Link: %a\n")
> > :clock-in t :clock-resume t :empty-lines 1)
> >
> > '("t2" "+ Ch02 Multi-Resolution Spectral Analysis" entry
> > (file+headline "~/02histr/tdr/02ch.rcl.org" "Tdr Document")
> > ,(concat "* Ch02 Multi-Resoln Spectr Anly\n"
> > " %^{Select |Augment:|Include:|Clarify:|Organise:} %?\n"
> > " Scheduled: %^T\n Entered: %T\n Link: %a\n")
> > :clock-in t :clock-resume t :empty-lines 1) )))
> >
> > (defun captr-tdr ()
> > (interactive)
> > (setq org-capture-templates captr-templ-tdr))
> >
> > (global-set-key (kbd "H-c") #'captr-tdr)
>
> To be honest that doesn't look good. Ha.
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2020-12-12 2:17 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 1:14 org-capture-templates constructed from three distinct functions Christopher Dimech
2020-12-12 1:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 2:05 ` Christopher Dimech
2020-12-12 2:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 2:17 ` Christopher Dimech [this message]
2020-12-12 2:21 ` Christopher Dimech
2020-12-12 2:30 ` Christopher Dimech
2020-12-12 2:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 2:43 ` Christopher Dimech
2020-12-12 2:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 3:00 ` Christopher Dimech
2020-12-12 3:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 9:02 ` tomas
2020-12-12 9:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-12 2:09 ` Christopher Dimech
2020-12-12 3:16 ` Michael Heerdegen
2020-12-12 3:24 ` Christopher Dimech
2020-12-12 3:43 ` Michael Heerdegen
2020-12-12 3:51 ` Christopher Dimech
2020-12-12 3:57 ` Michael Heerdegen
2020-12-12 4:02 ` Christopher Dimech
2020-12-12 4:14 ` Christopher Dimech
2020-12-12 4:18 ` Christopher Dimech
2020-12-12 4:31 ` Christopher Dimech
2020-12-12 4:54 ` Christopher Dimech
2020-12-12 22:47 ` Michael Heerdegen
2020-12-12 22:55 ` Christopher Dimech
2020-12-12 3:58 ` Christopher Dimech
2020-12-12 22:51 ` Michael Heerdegen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-949fcf58-8338-469c-a935-9401854ef87a-1607739470495@3c-app-mailcom-bs06 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).