From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: behavior of org-image-actual-size with units in attr_* :width
Date: Wed, 01 Oct 2014 19:51:31 -0400 [thread overview]
Message-ID: <m2h9znpcvw.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <877g0j8ubx.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Wed, 01 Oct 2014 21:26:42 +0200")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
is it the case that ATTR_HTML width attributes are only in pixels? If
so, that is certainly an easier modification to make, and would solve my
problem (we almost exclusively use attr_latex for that export).
Your comment inspired me to solve it this way:
#+attr_latex: :width 4in :placement [H]
#+attr_org: :width 400
[[./images/batch-multiple.png]]
For inline images, the attr_org is found first, but in latex export it
is ignored and it gets the width there.
Maybe no change is needed at all.
> Hello,
>
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
>> I have set this in my init file
>>
>> (setq org-image-actual-width '(600))
>>
>> It works great, unless I use:
>> #+attr_latex: :width 4in
>>
>> This makes my images 4 inches wide in LaTeX, but it sets my images to
>> approximately 4 pixels wide!
>>
>> I feel like it is worth modifying the regexp that gets the width to
>> catch these cases and fall back on the variable value when they
>> exist. Any thoughts?
>
> I wonder if this kludge makes any sense in the general case. As you
> noticed, units given in a LaTeX attributes line will probably be
> different from pixels.
>
> What about limiting the regexp to ATTR_HTML lines only?
>
>
> Regards,
--
-----------------------------------
John Kitchin
Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2014-10-01 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 21:09 behavior of org-image-actual-size with units in attr_* :width John Kitchin
2014-10-01 19:26 ` Nicolas Goaziou
2014-10-01 23:51 ` John Kitchin [this message]
2014-10-03 8:03 ` Nicolas Goaziou
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=m2h9znpcvw.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--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).