From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: visuweshm@gmail.com, 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 19:34:48 +0300 [thread overview]
Message-ID: <86cykufhw7.fsf@gnu.org> (raw)
In-Reply-To: <877cb2fj0c.fsf@gmail.com> (message from Robert Pluim on Mon, 23 Sep 2024 18:10:43 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: visuweshm@gmail.com, pinmacs@cas.cat, emacs-devel@gnu.org
> Date: Mon, 23 Sep 2024 18:10:43 +0200
>
> >>>>> On Mon, 23 Sep 2024 18:54:25 +0300, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> Cc: Visuwesh <visuweshm@gmail.com>, pinmacs@cas.cat, emacs-devel@gnu.org
> >> Date: Mon, 23 Sep 2024 17:09:03 +0200
> >>
> Eli> IMO, for users we already have what is needed: when we detect several
> Eli> formats, we show them to the user and ask him/her to tell us which
> Eli> format he/she wants to use.
> >>
> >> But that requires user interaction. I think the original request could
> >> be summed up as "if the list contains image/png, donʼt ask me, just
> >> insert the image".
>
> Eli> That's not how I understand the request. It was not always PNG, it
> Eli> was "sometimes PNG, but if so-and-so-happens, the JPEG" etc.
>
> Yes, but the "so-and-so" is determined by a user option. So
>
> 1. Always prefer "png" -> user option == "png"
> 2. Want to choose between "png" and "jpeg" -> user option == ("png"
> "jpeg")
> 3. All of the formats -> user option == nil
That makes little sense to me: how can the user decide in advance to
use only PNG? by what logic?
And anyway, this is not what the OP said. Let's get back to what he
said:
> Eli> And no one has explained yet why I would prefer PNG to JPEG or vice
> Eli> versa, btw. The usual choices I'm familiar with is whether or not to
> Eli> preserve typefaces, colors, and other fancy attributes; regarding
> Eli> images, there's just a decision whether you want to paste the material
> Eli> as a picture or as some kind of text, whether rich or not. So the
> Eli> background and the context for this request is still not clear to me.
>
> I can definitely see a use for case 1 above: "donʼt bother asking me,
> if png is available just use that".
I don't understand why would someone define their preference in the
terms of image format. It makes no sense.
next prev parent reply other threads:[~2024-09-23 16:34 UTC|newest]
Thread overview: 70+ 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
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 [this message]
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-10-26 17:27 ` Ihor Radchenko
2024-10-26 19:09 ` Eli Zaretskii
2024-10-27 8:17 ` Ihor Radchenko
2024-10-27 9:14 ` Eli Zaretskii
2024-10-27 9:36 ` Visuwesh
2024-10-27 10:09 ` Eli Zaretskii
2024-10-27 15:02 ` Visuwesh
2024-10-27 17:11 ` Eli Zaretskii
2024-10-28 13:37 ` Visuwesh
2024-10-29 11:29 ` Visuwesh
2024-10-30 23:22 ` Pedro
2024-10-31 8:29 ` Eli Zaretskii
2024-10-31 10:47 ` pinmacs
2024-10-31 11:16 ` Eli Zaretskii
2024-10-31 11:51 ` pinmacs
2024-10-31 14:31 ` Eli Zaretskii
[not found] ` <c67bb616-710b-4272-919d-bf4ece8e7c99@imayhem.com>
2024-10-31 14:20 ` Eli Zaretskii
2024-10-31 18:21 ` Ihor Radchenko
2024-10-31 19:03 ` Eli Zaretskii
2024-10-31 19:08 ` Ihor Radchenko
2024-10-31 19:29 ` Eli Zaretskii
2024-10-31 19:42 ` Ihor Radchenko
2024-11-01 7:01 ` Eli Zaretskii
2024-10-31 8:48 ` Visuwesh
2024-10-31 8:24 ` Eli Zaretskii
2024-10-31 8:46 ` Visuwesh
2024-10-31 9:56 ` Eli Zaretskii
2024-11-01 5:20 ` Visuwesh
2024-11-01 7:38 ` Eli Zaretskii
2024-11-03 17:19 ` Ihor Radchenko
2024-11-03 18:47 ` Eli Zaretskii
2024-11-04 4:04 ` Visuwesh
2024-11-04 20:03 ` Ihor Radchenko
2024-11-04 20:19 ` Eli Zaretskii
2024-10-28 18:39 ` Ihor Radchenko
2024-10-28 18:50 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cykufhw7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pinmacs@cas.cat \
--cc=rpluim@gmail.com \
--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 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.