From: daniela-spit@gmx.it
To: Jean Louis <bugs@gnu.support>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Org Capture Template
Date: Fri, 27 Nov 2020 07:43:27 +0100 [thread overview]
Message-ID: <trinity-7766327e-1137-4c8f-8988-31d815d6dca8-1606459407819@3c-app-mailcom-bs02> (raw)
In-Reply-To: <X8Cc6c6PXaDYO2fm@protected.rcdrun.com>
> Sent: Friday, November 27, 2020 at 7:30 AM
> From: "Jean Louis" <bugs@gnu.support>
> To: daniela-spit@gmx.it
> Cc: "Help Gnu Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Org Capture Template
>
> * daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-11-27 09:14]:
> > Yes, it seems better to do one long string, it was how I was doing things.
> > Afterwards, I thought that concat could help me to indent the string for cases
> > where it is too long. Is there any other way to be able to indent, rather than
> > using column number 1, when starting a new line?
>
> When doing customization or when writing some text? Or in programming
> modes?
>
> In customization I have no idea about indenting. Normally items are in
> field forms and person need not do complicated lists.
>
> Do you use the `customize' function to define org-capture-templates?
I just use as in example
(setq org-capture-templates
'(("t" "Todo" entry
(file "~/02history/rcl.org")
"* TODO %^{Heading}\n Brief: %^{Brief}\n
Detail: %?\n
Entered: %T\n Link: %a\n")))
> As it looks like below, pretty visible, easier to edit.
>
> Hide Org Capture Templates:
> INS DEL Choice: Value Menu Template entry:
> Keys : p
> Description : Protocol
> Capture Type : Value Menu Org entry
> Target location: Value Menu File & Headline:
> Filename : Value Menu Literal: ~/Documents/Orgnotes.org
> Headline: Inbox
> Template : Value Menu String: * %^{Title}
> Source: %u, %c
> #+BEGIN_QUOTE
> %i
> #+END_QUOTE
>
> If you use it directly in your config, then you have standard Emacs
> Lisp indentation. For strings you can do any how, but then do not
> invoke M-q to indent as it will ruin your own string chunk
> indentations.
>
> When there are longer strings with new lines I tend to define them this way:
>
> (let ((string "The heading
>
> Then anything else is here.
> I just keep writing straight from first column")))
>
> rather than using this way:
>
> (let ((string (concat "The heading\n\n"
> "Then anything else is here.\n"
> "I just keep writing straight from first column"))))
>
>
> And I mean longer strings than those above. For few lines I could
> be using similar method like you.
next prev parent reply other threads:[~2020-11-27 6:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 4:46 Org Capture Template daniela-spit
2020-11-27 5:34 ` Arthur Miller
2020-11-27 5:51 ` .Re: " daniela-spit
2020-11-27 6:51 ` Arthur Miller
2020-11-27 7:07 ` daniela-spit
2020-11-27 7:27 ` Arthur Miller
2020-11-27 7:48 ` daniela-spit
2020-11-27 8:55 ` Arthur Miller
2020-11-27 9:31 ` daniela-spit
2020-11-27 10:32 ` daniela-spit
2020-11-27 16:49 ` Arthur Miller
2020-11-27 17:46 ` daniela-spit
2020-11-27 19:52 ` daniela-spit
2020-11-27 21:03 ` Arthur Miller
2020-11-27 5:53 ` Jean Louis
2020-11-27 6:13 ` daniela-spit
2020-11-27 6:30 ` Jean Louis
2020-11-27 6:43 ` daniela-spit [this message]
2020-11-27 21:03 ` 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-7766327e-1137-4c8f-8988-31d815d6dca8-1606459407819@3c-app-mailcom-bs02 \
--to=daniela-spit@gmx.it \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
/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).