all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49347@debbugs.gnu.org, omar.i.elashkar@gmail.com
Subject: bug#49347: image-save not working as expected for transformed image saving!
Date: Mon, 05 Jul 2021 14:46:44 +0200	[thread overview]
Message-ID: <87v95pyll7.fsf@gnus.org> (raw)
In-Reply-To: <83y2amgoks.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Jul 2021 17:07:15 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Emacs can't current export the "real" image data -- see bug#44172 (which
>> I've now merged with this one).  It's not quite clear how to proceed
>> with that bug report, because we leave the transforms to the OS, so
>> Emacs doesn't have easy access to the actual displayed image data.
>
> Maybe just document the limitation for now?

If we plan to change what it does, perhaps we should just leave it
vague?  On the other hand, we could say "Currently the command saves the
original image data, but that may change in the future?"  Hm...  or
perhaps `C-u' could make the command switch to "save current data" if we
ever figure out how to implement that.

OK, I'll update the doc string.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-07-05 12:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  3:28 bug#49347: image-save not working as expected for transformed image saving! Omar Elashkar
2021-07-03  6:23 ` Eli Zaretskii
     [not found]   ` <CAFtvpMQxus01ehf+x_rNbSgyf2eNZ4CODvJNtnC4Jixizf6KkA@mail.gmail.com>
2021-07-03  6:46     ` Eli Zaretskii
2021-07-04 13:46       ` Lars Ingebrigtsen
2021-07-04 14:07         ` Eli Zaretskii
2021-07-05 12:46           ` Lars Ingebrigtsen [this message]

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=87v95pyll7.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=49347@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=omar.i.elashkar@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.