From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Support for something like org-image-max-width
Date: Mon, 02 Dec 2019 22:00:47 +0100 [thread overview]
Message-ID: <844kyil9xc.fsf@gmail.com> (raw)
In-Reply-To: 87wobfhj6s.fsf@gmail.com
Terje Larsen <terlar@gmail.com> writes:
> There is already org-image-actual-width but the problem with that one is
> that images that have quite small width, but are tall will be scaled and
> become very tall.
> I think it would make sense to introduce something like
> org-image-max-width, which would scale images that are larger than this
> width, but leave images within this width alone.
I think this is doable since there is already a max-width parameter for
images IIRC. But this means some work AFAICS. A way could be to allow
a pair like (max-width . 555) as org-image-actual-width with the meaning
to downsize any image wider than 555 and let the smaller images alone.
Could you invest some energy and possibly suggest a patch? You have all
the time.
> Another interesting thing would be to be able to adjust the max-width to
> the width of the buffer, but not sure how well that will play in all
> cases and how complex that would be.
This looks also doable AFAICT.
FWIW I use a little extension of the image-map which allows to adjust
the image width with the window-width with key "W" on the image. (Quite
a bunch of w's in that sentence.)
This is the respective code from my init file:
#v+
(defun mw-image-change-width-to-window-width ()
"Resize image width to match window-width."
(interactive)
(let* ((image (image--get-image))
(new-image (image--image-without-parameters image)))
(setcdr image (cdr new-image))
(plist-put (cdr image) :width (nth 2 (window-inside-pixel-edges)))))
(define-key image-map "W" #'mw-image-change-width-to-window-width)
#v-
next prev parent reply other threads:[~2019-12-02 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-01 20:42 Support for something like org-image-max-width Terje Larsen
2019-12-02 21:00 ` Marco Wahl [this message]
2024-07-26 7:24 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=844kyil9xc.fsf@gmail.com \
--to=marcowahlsoft@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).