emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [bug] Should #+attr_latex affect image display within the org buffer itself?
Date: Tue, 26 May 2020 12:06:29 +0800	[thread overview]
Message-ID: <CA+A2iZaR7PL1fLbUFbZaY01J65uBedpo--C1MJSdz3DY=1LdNQ@mail.gmail.com> (raw)
In-Reply-To: <CA+A2iZZuNM1e5hNCPbwiReQD71mKKcB4nS9jaAgoL0ZMeeDXBQ@mail.gmail.com>

At the moment, I'm working around this by setting the width in "TeX points":

#+attr_latex: :width 224pt

The exported image becomes 224 points wide (roughly 8 cm), and the
embedded image is 224 pixels wide, which is okay.

2020-05-26 12:01 GMT+08:00, Vladimir Nikishkin <lockywolf@gmail.com>:
> Hello, everyone
> My problem is the following:
> Compare the following three pieces of  org code:
> #+attr_latex: :width 80px
> [[file:figure-1-1-dot.png]]
> #+attr_latex: :width 8cm
> [[file:figure-1-1-dot.png]]
> #+attr_latex: :width 80mm
> [[file:figure-1-1-dot.png]]
> They get exported into LaTeX as expected.
> But if you org-redisplay-inline-images, you will see that the first
> one is rendered 80 pixels wide,
> the second one ise rendered 8 pixels wide, and the third one is
> rendered 80 (again) pixels wide.
> So it seems that org is using #+attr_latex as a guide in setting the
> width of the images in the org-buffer.
> This seems wrong.
> --
> Yours sincerely, Vladimir Nikishkin

Yours sincerely, Vladimir Nikishkin

  reply	other threads:[~2020-05-26  4:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  4:01 [bug] Should #+attr_latex affect image display within the org buffer itself? Vladimir Nikishkin
2020-05-26  4:06 ` Vladimir Nikishkin [this message]
2020-05-26 16:54   ` John Kitchin

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:

  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='CA+A2iZaR7PL1fLbUFbZaY01J65uBedpo--C1MJSdz3DY=1LdNQ@mail.gmail.com' \
    --to=lockywolf@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).