From: Timothy <firstname.lastname@example.org> To: Matt Huszagh <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com> Subject: Re: Why is an image width restricted to being between 0 and 200% of the text area Date: Tue, 23 Nov 2021 15:01:48 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1286 bytes --] Hi Matt, > I agree that requesting an image to be >2x the buffer text width is a > strange request, and it’s not one I’ve ever tried to give. But, I think > the salient point is that it’s a very clear request, and I think org > should carry it out. I’m all in favor of org helping people not shoot > themselves in the foot, but I don’t think it should prevent people from > doing so, especially when they’re clear about their intentions. I also > think this qualifies as a case where someone /might/ have a valid reason > for doing this. 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! 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. All the best, Timothy
next prev parent reply other threads:[~2021-11-23 7:07 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-23 6:16 Matt Huszagh 2021-11-23 6:17 ` Timothy 2021-11-23 7:00 ` Matt Huszagh 2021-11-23 7:01 ` Timothy [this message] 2021-11-23 7:21 ` Matt Huszagh 2021-11-23 8:14 ` Tim Cross 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Why is an image width restricted to being between 0 and 200% of the text area' \ /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
Code repositories for project(s) associated with this 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).