emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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 23:30:33 -0500	[thread overview]
Message-ID: <1a4f7d7b925c853e381437ebc5fa1502@isnotmyreal.name> (raw)
In-Reply-To: <trinity-9343a8fe-9db1-47db-8cb3-c6521ce93dfe-1607831362919@3c-app-mailcom-bs11>

On 2020-12-12 22:49, pietru@caramail.com wrote:
> TRS-80 wrote:
>> 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):
> It was an example for long agenda option.  Wanted to send a basic one
> without the details that could bother you.  The real one will have
> information regarding Site_Type [Domestic, Funerary, Water-Related,
> Settlement].  But we don't have the things in org though.

It's no bother.  In fact I am already thinking ahead as to the structure
of the data, which is the most important consideration.  Choice of
tool(s) should flow from that, and also from the desired workflow,
instead of the other way around.

Just so you know, you /could/ have the things in Org, if you wanted to
(or even in a separate plain text file, and use that as input for your
narrowing selection list).  Maybe they change, or there are other
reasons, but you could have the options in a list to choose from.  This
sort of thing reduce typos and errors.  You could limit to such list
strictly, or not (the latter allowing flexibility to add things on the

>> 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.  :)
> Yes, I know about " %^{Investigation Type: |Site
> Stabilization|Heritage Management|Environment Research} %?\n"

I am beginning to suspect you have bigger data and more options than fit
comfortably into a capture template.  I could be wrong, but in my mind
at least, the idea of capture templates is to quickly store small ideas,
notes, TODOs, etc. so you can go back to what you were working on in the
first place, with minimal interruption to your original train of

> Data can then be parsed into database once we get tho data files at 
> home
> base.

True, however well designed "capture" mechanism (in reality, data
structure) will make this job much easier.

> What sort of thing better than template capture?  My basic idea was to 
> see
> what org tools are available, see what kind of problems me get to, 
> without
> asking too much things specific to us.  We can then work through things
> ourselves.  Perhaps share them with some other organisations.

As I mentioned in last mail, I think Org Properties might be more what
you might be looking for.  You may or may not even need any custom Elisp
in addition to that.

>> [1] https://orgmode.org/manual/Properties-and-Columns.html

Try and just play around with that, create some heading and do
org-set-property and then enter a key and value.  If you want to set a
list to choose from, you put at top of file something like:

#+PROPERTY: Investigation_Type_ALL Site_Stabilize Heritage_Management
#+PROPERTY: District_ALL 1 2 3
#+PROPERTY: Site_Type_ALL Domestic Funerary Water-Related Settlement

You may need to press C-c C-c within the above to re-load and make it

If you like something like that, it's easy to copy blank template and
just open new one for each survey or whatever you are doing and go from
there.  And then here is where Emacs and Orgmode really shine, as they
are unparalleled as note taking tools.  You can include pictures,
tables, etc. headlines and lists, etc.  But you probably know all that


  reply	other threads:[~2020-12-13  4:31 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
2020-12-13  3:49         ` pietru
2020-12-13  4:30           ` TRS-80 [this message]
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:

  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=1a4f7d7b925c853e381437ebc5fa1502@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --cc=emacs-orgmode@gnu.org \


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