From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: yank-media: allow users to limit image types that can be inserted Date: Sun, 27 Oct 2024 08:17:22 +0000 Message-ID: <874j4yot7x.fsf@localhost> References: <79fc91f3-c2c3-44db-9817-595808917f26@cas.cat> <86ed5ahb08.fsf@gnu.org> <87zfnywki8.fsf@gmail.com> <86setqfnmq.fsf@gnu.org> <87frpqflv4.fsf@gmail.com> <86ikumfjri.fsf@gnu.org> <877cb2fj0c.fsf@gmail.com> <86cykufhw7.fsf@gnu.org> <3a015d0f-549a-401f-be1c-651c9dbd5d9a@cas.cat> <8634lqfcaf.fsf@gnu.org> <87ikulwsd6.fsf@gmail.com> <86o74ddzxp.fsf@gnu.org> <87msiqvkph.fsf@localhost> <86ed42bs03.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7271"; mail-complaints-to="usenet@ciao.gmane.io" Cc: visuweshm@gmail.com, pinmacs@cas.cat, rpluim@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 27 09:16:38 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1t4yRx-0001gi-Ca for ged-emacs-devel@m.gmane-mx.org; Sun, 27 Oct 2024 09:16:37 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1t4yR8-0002bP-Cs; Sun, 27 Oct 2024 04:15:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t4yR5-0002bA-SX for emacs-devel@gnu.org; Sun, 27 Oct 2024 04:15:44 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1t4yR4-0006A7-6M for emacs-devel@gnu.org; Sun, 27 Oct 2024 04:15:43 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 7D332240027 for ; Sun, 27 Oct 2024 09:15:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1730016938; bh=BEux6OslcoDn+DAk5AAyj5NcHDh0RCyX4eQuTMsLvh0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=E7a/U85U0rNW9SNPcbaLVw/c8nEihSMFjHvyA0x/6LY+6Tr59KiGEEN3GmLTaCpoW Ib+wmwyT+co6yRugj+xP7/uvP8+We5uVOFmgjwjXiB1ua/+TFzslNY21unuVGyDZH/ ddLSfGHc6c/QD7pYEMkYqIR1n8gdExvVlgwsDtfisjC47YYU/pboiAANQgJUz71Dl6 s8e1cmZfwXrylzS6y1QX1VrtwlocL7GM+ErTktyPLi7brcneMOJ6Vcbw2qQcqgOJ0V f0BSqR8q0pEbywXH3hh9vcfCzAUQtXqV+cy98D8MzvG56nmJ9m2Z5PVT3NOxTj99+2 tCY/hU2uSdtJQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4Xbq8T5CFpz6tsg; Sun, 27 Oct 2024 09:15:37 +0100 (CET) In-Reply-To: <86ed42bs03.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:324872 Archived-At: Eli Zaretskii writes: > >> Does it mean that you are not against an equivalent variable that can be >> used from Elisp? I think that it might be good enough for Org mode >> purposes and, if deemed necessary, may be later converted to user option. > > If a Lisp program wants to control which MIME types are preferred, it > can do that already by changing the list of handlers, no? I'm sure I > said that at some point in the discussion. Let me try to explain in my own words. Consider the following 3 scenarios: 1. clipboard contains 2 MIME types: image/png, image/bmp 2. clipboard contains 1 MIME type: image/png 3. clipboard contains 1 MIME type: image/bmp We want to handle all three scenarios in the following way: 1. Select image/png (prefer it over image/bmp) 2. Select image/png 3. Select image/bmp (there is no image/png that we would prefer otherwise) In all three cases, we do not want to prompt user about mimetype choice. How can we do it using the existing Elisp API? > [It's hard to pick up a discussion which stopped a month ago.] Aside: It is not the first time you mention this problem, and I am wondering how can it be. The full discussion is recorded in the mailing list archives and possibly available from your MUA from thread view (is it not?). -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at