emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] New remote resource download policy
Date: Thu, 30 Jun 2022 23:57:58 +0700	[thread overview]
Message-ID: <t9kkmn$895$1@ciao.gmane.io> (raw)
In-Reply-To: <87o7yb7af2.fsf@gmail.com>

On 29/06/2022 22:27, Timothy wrote:
> Max Nikulin writes:
> I also really don’t like how `org-mks' so forcefully grabs all keyboard input. I
> can see it being nice to jump back to the buffer and see where the resource is
> being used, which isn’t really possible using `org-mks'.

An idea: a menu entry that displays location in the org file that caused 
the prompt. However it may require enough work to pass context data to 
the function rendering menu.

I see you point concerning blocking modal prompt and I do not like it as 
well. Have you seen the following thread:

Arthur Miller. Proposal: 'executable' org-capture-templaes. Wed, 22 Jun 
2022 14:13:51 +0200.

If it were merged already, would it be enough for you to implement the 
dialog or the proposal lacks some features necessary for smooth user 

The reason why I asked about `org-mks' is expectation of UI consistency 
withing Org. It might help users having customized `display-buffer-alist'

Eric S Fraga. Re: Bug: org-no-popups disregards 
display-buffer-fallback-action Sun, 14 Nov 2021 19:37:30 +0000.

Eric S Fraga. window management for logging and capturing notes. Sun, 10 
Oct 2021 18:01:56 +0100.

I still do not like code adding a menu close enough to existing one, but 
I will not object any more.

  reply	other threads:[~2022-06-30 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-12 14:43 [PATCH] New remote resource download policy Timothy
2022-06-12 16:18 ` Daniel Fleischer
2022-06-14  9:40 ` Robert Pluim
2022-06-22  9:58   ` Timothy
2022-06-15 12:35 ` Max Nikulin
2022-06-22 10:01   ` Timothy
2022-06-22 16:55     ` Max Nikulin
2022-06-29 15:27       ` Timothy
2022-06-30 16:57         ` Max Nikulin [this message]
2022-07-16  9:47           ` Timothy
2022-06-25  7:50     ` Max Nikulin

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='t9kkmn$895$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --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).