emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Huszagh <huszaghmatt@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: , "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Why is an image width restricted to being between 0 and 200% of the text area
Date: Mon, 22 Nov 2021 23:21:57 -0800	[thread overview]
Message-ID: <87mtlvpca2.fsf@gmail.com> (raw)
In-Reply-To: <87y25fjqqn.fsf@gmail.com>

Timothy <tecosaur@gmail.com> writes:

> It occurred to me that large values would only really appear when occurring in a
> narrower scope, e.g. in a multi-column document an image which is multiple
> columns wide. Say,
> ┌────
> │ #+attr_latex: 3.0\columnwidth
> └────
>
> However, I doubt that when previewing the image in Org one would want the
> preview to be 3x the buffer text area width!

Good point. I could see someone using this as an argument against
interpreting :width 3.0\columnwidth as :width 3.0, but I do see the
value in interpreting :width 0.8\linewidth as :width 0.8, so I don't
know.

> I suppose the exception would be say something like
> ┌────
> │ #+attr_org: :width 300%
> └────
> Though I can’t imagine why you’d want that…
>
> I think you don’t raise an unreasonable point, however I’m tempted to let this
> sit till we hear from someone who actually runs into this as an issue.

Yeah I think that makes sense. Thanks for considering this anyway!

Matt


  reply	other threads:[~2021-11-23  7:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23  6:16 Why is an image width restricted to being between 0 and 200% of the text area Matt Huszagh
2021-11-23  6:17 ` Timothy
2021-11-23  7:00   ` Matt Huszagh
2021-11-23  7:01     ` Timothy
2021-11-23  7:21       ` Matt Huszagh [this message]
2021-11-23  8:14     ` Tim Cross
  -- strict thread matches above, loose matches on Subject: below --
2021-11-23 11:16 autofrettage

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=87mtlvpca2.fsf@gmail.com \
    --to=huszaghmatt@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@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 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).