all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: pietru@caramail.com
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Org Capture Menu cannot be fully viewed
Date: Mon, 14 Dec 2020 14:00:05 +0100	[thread overview]
Message-ID: <trinity-c06a2de7-f5dd-4df3-9694-60570da8fafe-1607950805850@3c-app-mailcom-bs08> (raw)
In-Reply-To: <87pn3cd0fk.fsf@gmail.com>



> Sent: Monday, December 14, 2020 at 1:41 PM
> From: "Marco Wahl" <marcowahlsoft@gmail.com>
> To: pietru@caramail.com
> Cc: "Org-Mode mailing list" <emacs-orgmode@gnu.org>
> Subject: Re: Org Capture Menu cannot be fully viewed
>
> Hi Pietru and 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.
>
> Thanks for reporting.
>
> I just committed a fix along the lines of the similar exporter-UI and
> the agenda chooser-UI. Now there is at least C-n, C-p, C-v when the
> window is too small for all the items.
>
> Unfortunately these similar UIs are not unified when looking at the code
> base. E.g. I could not find a simple way to add key M-v to scroll one
> page up for the capture menu.
>
> Possibly these UIs could be unified or Org could even switch to
> something different. I think you already discussed some ideas. Sorry if
> I did not read the whole thread. That was too much information for me.

Don't worry about it.  I thank you for taking an interest towards a fix.

> Would be great if you could check out the fix.

Of coarse.  Is the following command the right way to get the fix
for testing?

git clone https://code.orgmode.org/bzg/org-mode.git


> Thanks and HTH,
> --
> Marco
>


  reply	other threads:[~2020-12-14 13:01 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
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 [this message]
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-c06a2de7-f5dd-4df3-9694-60570da8fafe-1607950805850@3c-app-mailcom-bs08 \
    --to=pietru@caramail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=marcowahlsoft@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.