emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: autofrettage <autofrettage@protonmail.ch>
To: "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: Tue, 23 Nov 2021 11:16:41 +0000	[thread overview]
Message-ID: <0EIkYJdN3eiT755CXExWoUf_KyUk4WhHGceG6b0V4W4JYsZxefgbMqnQCZ-SHJAxggpaBZ4hjE6HDs7WE7JI0jWR6zUnGNOKY6KHXM6ab9A=@protonmail.ch> (raw)

Hi,

If org mode won't blow up, kick out the restriction.

It is not up to us to decide what users will have use for or not. Besides, if someone specifies an outrageously wide picture by mistake, it's a mistake which is easy to spot and fix.

I finish my argument with a small war story. Many years ago  my colleagues and I tried to create a computational grid around a ship, for flow simulations. However, the grid generation program refused to follow our instructions, no matter what we tried. We reported this to the company behind the grid generation software, and it turned out they had imposed a 1000 m size limit on grids.

It just so happens that many merchant ships are almost 400 m long, and when you extend the computational grid sufficiently up- and downstream, you get a grid well over 1000 m long. Given the magnitude limit for double precision floating point numbers, 1000 m was a ridiculous limit.

yours
Rasmus


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 11:16 autofrettage [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2021-11-23  8:14     ` Tim Cross

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='0EIkYJdN3eiT755CXExWoUf_KyUk4WhHGceG6b0V4W4JYsZxefgbMqnQCZ-SHJAxggpaBZ4hjE6HDs7WE7JI0jWR6zUnGNOKY6KHXM6ab9A=@protonmail.ch' \
    --to=autofrettage@protonmail.ch \
    --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).