all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Jean Louis <bugs@gnu.support>
Cc: Tim Cross <theophilusx@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Org Capture Menu cannot be fully viewed
Date: Sun, 13 Dec 2020 19:46:10 +0100	[thread overview]
Message-ID: <trinity-3f06f753-26ae-4712-97a1-cf1c3740640e-1607885170545@3c-app-mailcom-bs09> (raw)
In-Reply-To: <X9XigBscC87S/ikS@protected.rcdrun.com>

> Sent: Sunday, December 13, 2020 at 10:44 AM
> From: "Jean Louis" <bugs@gnu.support>
> To: pietru@caramail.com
> Cc: "Tim Cross" <theophilusx@gmail.com>, emacs-orgmode@gnu.org
> Subject: Re: Org Capture Menu cannot be fully viewed
>
> * pietru@caramail.com <pietru@caramail.com> [2020-12-13 05:09]:
> > 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")
> > 
> >  ("b" "Systematic Survey Data Recovery/Excavation" entry
> >   (file "~/histr/archaeol.org")
> >   "* Site_Type: %?\n %T\n")
> 
> Your example is good real world practical example.
> 
> The capture menu was designed in the same degraded way as Org agenda
> menu. Difference is that Capture menu is customizable and not meant
> for users like you who need more than few categories. It is not
> expandable.
> 
> Would the menu be made as read only Org displayed in a buffer then:
> 
> - Emacs interface, such as using other windows during capture process,
>   would not be blocked during Capture selection
> 
> - User could at least scroll or enlarge the buffer what currently does
>   not work
> 
> Comparing it to my Hyperscope system if I wish to file or capture
> anything I may choose any set where to file it by using completion
> function which dwelles below in `hyperscope-select-set'. I am using
> semantic or meaning related search.
> 
> (defun hyperscope-add-note-to-set ()
>   (interactive)
>   (let ((parent (hyperscope-select-set)))
>     (hlink-add-generic name nil 9 parent nil note)))
> 
> When key press is invoked I am capturing a note or some other type of
> a node into a set. Could be anything, it could be URL, Action similar
> to TODO, note, file, picture, voice note, just anything:
> 
> - press key
> 
> - type what you think where it should be filed, press ENTER on selection
> 
> - edit the note
> 
> Description of `org-capture'
> 
> org-capture is an autoloaded interactive compiled Lisp function in
> ‘org-capture.el’.
> 
> It is bound to C-c c.
> 
> (org-capture &optional GOTO KEYS)
> 
> Capture something.
> 
> This will let you select a template from ‘org-capture-templates’, and
> then file the newly captured information.  The text is immediately
> inserted at the target location, and an indirect buffer is shown where
> you can edit it.  Pressing ‘C-c C-c’ brings you back to the previous
> state of Emacs, so that you can continue your work.
> 
> -----------
> 
> In your case "This will NOT let you select a template from
> org-capture-template". Function org-capture is written more in
> structured way of programming than functional way. It wants to do
> everything for user at once.
> 
> https://en.wikipedia.org/wiki/Structured_programming
> versus
> https://en.wikipedia.org/wiki/Functional_programming
> 
> What is here missing is `org-capture-by-completing-read' so that
> user may select among many various capture templates.
> 
> Compensating for initial bad design is expensive effort.

It looks that way. 
 
> Jean
> 

---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


  reply	other threads:[~2020-12-13 18:47 UTC|newest]

Thread overview: 54+ 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 20:57 ` bug#45215: " 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-3f06f753-26ae-4712-97a1-cf1c3740640e-1607885170545@3c-app-mailcom-bs09 \
    --to=dimech@gmx.com \
    --cc=bugs@gnu.support \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.