From: Timothy <firstname.lastname@example.org>
To: Max Nikulin <email@example.com>
Subject: Re: [PATCH] New remote resource download policy
Date: Sat, 16 Jul 2022 17:47:47 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1480 bytes --]
I’ve just made a few more tweaks, tested it, and pushed this as 0583a0c. We may
want to tweak this further before the next Org release, but I think this is a
good enough starting point.
> 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.
This could be added in future.
> 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 experience?
I have not read much of this thread, but from a brief glance — possibly.
> The reason why I asked about `org-mks’ is expectation of UI consistency withing
> Org. It might help users having customized `display-buffer-alist’
Here I was more thinking of UI consistency within Emacs.
> I still do not like code adding a menu close enough to existing one, but I will
> not object any more.
Since this is separate to the functionality, I’m going to push this for now, and
we can update the UI side of things later.
All the best,
next prev parent reply other threads:[~2022-07-16 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 14:43 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
2022-07-16 9:47 ` Timothy [this message]
2022-06-25 7:50 ` Max Nikulin
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).