From: Jean Louis <firstname.lastname@example.org>
To: TRS-80 <email@example.com>
Subject: Re: Org Capture Menu cannot be fully viewed
Date: Sun, 13 Dec 2020 14:06:00 +0300 [thread overview]
Message-ID: <X9X1mBQIJOM43Wx7@protected.rcdrun.com> (raw)
* TRS-80 <firstname.lastname@example.org> [2020-12-13 01:11]:
> On 2020-12-12 13:02, email@example.com wrote:
> > Dear All,
> > When making a relatively long Org Capture Menu for Archaeological
> > Field Management, the relevant capture window cannot be scrolled down.
> > This becomes particularly problematic with small field laptops.
> Hi Pietru,
> Capture templates are great, but I suppose there are a lot of advantages
> to doing some custom Elisp which is why I do a lot more stuff that way
> now that I have learned a little bit of Elisp.
I find myself there. Things that are great in Emacs need not be really
practically great, that is why we need to make things great again.
In other words program like Org capture is not meant for people having
too many templates and that shall be explained right away both in
function definitions and in the manual. Important people lose their
time and effort in customizing org capture which was not meant to be
used by people with too many templates.
Which turns back to exact subject of that email. Now question is who
is going to improve it? Can it be done better?
Can interface be improved that people with larger number of templates
become free to use it?
My proposal is to quit using blocking interface where user cannot move
from buffer to buffer, instead to open up new buffer with new key mode
map that assigns those keys to those capture template functions. That
way the buffer becomes unlimited, user can open it, it is familiar
org-mode buffer and it can be unlimited.
> Sorry, I guess that's not helpful if you are not comfortable with
> Elisp. As an aside and thinking long term, I can say the investment
> was well worth the payoff. However back to the issue at hand.
I have also realized, that is why I have dropped the Org mode for
planning and project management, including for capturing notes.
> Maybe if you are willing (or able) to share some more information, we
> could help you through some basics. Or maybe someone else might even
> have some better idea (not involving Elisp) which might be more
> appealing to you.
Why not provide completing-read for Org capture templates? That would
solve the problem fully.
next prev parent reply other threads:[~2020-12-13 17:34 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 [this message]
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
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
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 \
* 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).