From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Org Capture Menu cannot be fully viewed
Date: Sat, 12 Dec 2020 22:16:32 -0500 [thread overview]
Message-ID: <f6908a25561506cc39643915582c6eaa@isnotmyreal.name> (raw)
In-Reply-To: <trinity-66876af5-d8b2-42fd-950b-9e5f95c1bda3-1607825300196@3c-app-mailcom-bs06>
On 2020-12-12 21:08, pietru@caramail.com wrote:
> Here is one version of a template
>
> (setq capture-template-investigation-type '(
>
> ("a" "Historic Background Research Site Evaluation/Testing" entry
> (file "~/histr/archaeol.org")
> "* Site_Type: %?\n %T\n")
>
> [...]
>
> ("u" "Remote Sensing" entry
> (file "~/histr/archaeol.org")
> "* Site_Type: %?\n %T\n") ))
>
Are there any more to these templates you did not show?
Because, (and unless I am missing something) what I see are essentially
all the same (and quite simple). You would end up with something like
the following in your target file (with the cursor ending up at the x):
#+begin_example
* Site_Type: x
[2020-12-12 Sat 21:58]
#+end_example
In fact I don't even see where the type name ends up in the result?
If all my assumptions above are true, I think you would probably be
better served with a simple completing-read (or similar) function to
select the "Investigation Type" from a list and then simply insert that
along with a timestamp. Which it will take you longer to reply to this
email and confirm than it would take me to write such a function. :)
Benefit of that way also removes possibility of typos in the type name.
In fact, the above could even be done with something as simple as
Yankpad[0].
I have no idea what your workflow looks like, or where this data ends
up. However, thinking further, I would imagine it might even be helpful
to set one or more Org properties[1] for things like "Investigation
Type" (along with some other things I could speculate like "Location"
etc.). But all of that depends on even more things I don't know about.
If you care to share a slightly bigger picture view, particularly about
the structure of the data you are trying to capture (and/or, your
workflow) we could likely come up with something that would work much
better for you than a capture template, at least in this particular
case.
Cheers,
TRS-80
[0] https://github.com/Kungsgeten/yankpad
[1] https://orgmode.org/manual/Properties-and-Columns.html
next prev parent reply other threads:[~2020-12-13 3:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 18:02 Org Capture Menu cannot be fully viewed pietru
2020-12-12 22:09 ` TRS-80
2020-12-12 22:46 ` pietru
2020-12-12 23:13 ` TRS-80
2020-12-12 23:30 ` pietru
2020-12-13 0:00 ` TRS-80
2020-12-13 0:10 ` pietru
2020-12-13 11:06 ` Jean Louis
2020-12-13 18:28 ` pietru
2020-12-13 20:37 ` Jean Louis
2020-12-13 20:52 ` TRS-80
2020-12-13 21:02 ` pietru
2020-12-13 21:48 ` Jean Louis
2020-12-13 22:08 ` pietru
2020-12-13 22:20 ` pietru
2020-12-13 22:00 ` TRS-80
2020-12-13 22:36 ` pietru
2020-12-13 20:32 ` TEC
2020-12-13 21:43 ` Jean Louis
2020-12-13 0:46 ` Tim Cross
2020-12-13 1:32 ` pietru
2020-12-13 2:08 ` pietru
2020-12-13 3:16 ` TRS-80 [this message]
2020-12-13 3:49 ` pietru
2020-12-13 4:30 ` TRS-80
2020-12-13 9:58 ` pietru
2020-12-13 16:52 ` Jean Louis
2020-12-13 10:24 ` Jean Louis
2020-12-13 18:41 ` pietru
2020-12-13 20:48 ` TRS-80
2020-12-13 4:57 ` pietru
2020-12-13 9:24 ` Christopher Dimech
2020-12-13 23:08 ` TRS-80
2020-12-14 0:04 ` pietru
2020-12-13 9:44 ` Jean Louis
2020-12-13 18:46 ` Christopher Dimech
2020-12-16 18:46 ` No Wayman
2020-12-16 16:58 ` No Wayman
2020-12-13 15:12 ` Jean Louis
2020-12-13 18:08 ` pietru
2020-12-13 20:06 ` Tim Cross
2020-12-13 21:37 ` pietru
2020-12-13 21:57 ` Bastien
2020-12-13 22:31 ` pietru
2020-12-13 23:30 ` Jean Louis
2020-12-13 23:52 ` Bastien
2020-12-13 22:34 ` Jean Louis
2020-12-14 12:41 ` Marco Wahl
2020-12-14 13:00 ` pietru
2020-12-14 13:18 ` Marco Wahl
2020-12-14 20:02 ` Org Capture Menu cannot be fully viewed - Results of testing C-n, C-p, C-v pietru
2020-12-16 21:46 ` Marco Wahl
2020-12-16 23:25 ` pietru
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=f6908a25561506cc39643915582c6eaa@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--cc=emacs-orgmode@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.
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).