From: Robert Pluim <rpluim@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, pinmacs@cas.cat, emacs-devel@gnu.org
Subject: Re: yank-media: allow users to limit image types that can be inserted
Date: Mon, 23 Sep 2024 17:20:38 +0200 [thread overview]
Message-ID: <87bk0eflbt.fsf@gmail.com> (raw)
In-Reply-To: <87r09awgfo.fsf@gmail.com> (Visuwesh's message of "Mon, 23 Sep 2024 20:44:19 +0530")
>>>>> On Mon, 23 Sep 2024 20:44:19 +0530, Visuwesh <visuweshm@gmail.com> said:
Visuwesh> [திங்கள் செப்டம்பர் 23, 2024] Robert Pluim wrote:
Eli> The issue at hand here, AFAIU, is not the UI, but how Lisp programs
Eli> (and Org in particular) can control this. If the issue is the user
Eli> interface, then I honestly don't understand what issue is being
Eli> brought up, because in that case we already have the correct and
Eli> comprehensive solution, similar to what other advanced apps do in
Eli> these cases.
>>
>> You have to register the yank-media-handler before the yank-media
>> call, so org canʼt control this: it has to register for "image/.*"
>> because it canʼt know what formats will be presented to it. I guess it
>> could have a user option to filter the results from inside its
>> yank-media-handler, but then *every* package that wants to support
>> image yanking will have to implement something similar: we should just
>> implement such handling in the yank-media code.
Visuwesh> AFAIR the yank-media code, there's no way for the handlers to reject a
Visuwesh> specific format. yank-media, the command, asks the user the type she
Visuwesh> wants, _then_ calls the handler specific to that type. The handler
Visuwesh> cannot influence anything during this interaction.
Youʼre right. So even more reason to put such filtering in the
yank-media code.
Robert
--
next prev parent reply other threads:[~2024-09-23 15:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 16:53 yank-media: allow users to limit image types that can be inserted pinmacs
2024-09-23 11:20 ` Eli Zaretskii
2024-09-23 13:46 ` Visuwesh
2024-09-23 14:30 ` Eli Zaretskii
2024-09-23 15:06 ` Visuwesh
2024-09-23 15:48 ` Eli Zaretskii
2024-09-23 15:09 ` Robert Pluim
2024-09-23 15:14 ` Visuwesh
2024-09-23 15:20 ` Robert Pluim [this message]
2024-09-23 15:58 ` Eli Zaretskii
2024-09-24 5:00 ` Visuwesh
2024-09-24 5:10 ` Visuwesh
2024-09-24 11:57 ` Eli Zaretskii
2024-09-24 12:42 ` Visuwesh
2024-09-23 15:54 ` Eli Zaretskii
2024-09-23 16:10 ` Robert Pluim
2024-09-23 16:34 ` Eli Zaretskii
2024-09-23 18:00 ` pinmacs
2024-09-23 18:35 ` Eli Zaretskii
2024-09-23 20:45 ` Pedro
2024-09-23 21:08 ` pinmacs
2024-09-24 8:15 ` Robert Pluim
2024-09-24 11:30 ` Eli Zaretskii
2024-09-24 12:18 ` Robert Pluim
2024-09-24 13:08 ` Eli Zaretskii
2024-09-24 13:38 ` Visuwesh
2024-09-24 13:50 ` Eli Zaretskii
2024-09-24 5:08 ` Visuwesh
2024-09-24 12:00 ` Eli Zaretskii
2024-09-24 12:50 ` Visuwesh
2024-09-24 13:23 ` Eli Zaretskii
2024-09-24 13:37 ` Visuwesh
2024-09-23 18:11 ` Eli Zaretskii
2024-09-24 8:38 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bk0eflbt.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pinmacs@cas.cat \
--cc=visuweshm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).