Date: Thu, 31 Oct 2024 00:22:57 +0100
From: Pedro <pedro@cas.cat>
The approach of this patch permits to have different yank commands with
different keybindings and context to respond to different needs (For the
things I care, I end up having two commands, one that is simple and fast
with the most preferred thing; and the other that gives all flexibility
and possibilities). So, happy to see flexibility here too.
Flexibility doesn't come for free, though: are you arguing for having
N yank-media commands, each with its own preference of media formats?
Which means the user will have to remember the preferences for each
command and allocate a separate key binding to each? How is that a
good thing?
It might be useful to know why this is better: it is less error prone to
what I have now. Let me explain this: the other day, by mistake (being
in a hurry) I did several screen captures and I thought I was using .png
(I usually pick png on the first time, and then, by frequency, it
appears in the first position because of the completion tool
(vertico/orderless ?)). But I was wrong, I took .pbm, for that case,
that was fine, it was notes for me, but it could be the case of having
screen captures with the wrong format and having difficulty to generate
them again. This patch and approach helps the user to avoid that risk.
I don't understand that: how is the image format of the screen capture
relevant to yanking images into an Emacs buffer? What am I missing?