From: William Denton <wtd@pobox.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [O] What happened to ATTR_ORG?
Date: Tue, 13 Jul 2021 14:06:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2107131404360.58488@shell3.miskatonic.org> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2107131311380.58332@shell3.miskatonic.org>
[-- Attachment #1: Type: text/plain, Size: 3523 bytes --]
Sorry, that escaped too soon. I meant to say that
#+attr_org: :width 300
wasn't resizing the images in the Org buffer to 300 pixels wide. Turned out it
wasn't Imagemagick, it was the variable org-image-actual-width, which was set to
ignore any attr_* directives. I changed that and now it's working.
Bill
On 13 July 2021, William Denton wrote:
> Following up on this two years later ...
>
> I had some images that I wanted to shrink in my Org buffer, but
>
> #+attr_org:
>
> (setq org-image-actual-width nil)
>
> I had the variable set to t: "When non-nil, use the actual width of images
> when inlining them." There are a few other options, but nil does what I
> want: "When set to nil, try to get the width from an #+ATTR.* keyword and
> fall back on the original width if none is found."
>
> Bill
>
> On 25 May 2019, Cheong Yiu Fung wrote:
>
>> I'm using the latest Org and it's working. If you'd like to dig the
>> cause you might want to dig in `org-display-inline-images'. It accepts
>> `:width' in any #+ATTR.*-like option, then immediately call
>> `create-image'. I would guess it's an imagemagick problem too.
>>
>> steen <mediapathic@gmail.com> writes:
>>
>>> I am also having the same issue. I don't have time right now to try to
>>> track down causes, but this is not a unique problem. The behavior I am
>>> seeing is that #+ATTR_ORG no longer causes the images to be resized, they
>>> display at original size.
>>> -- Steen
>>>
>>>
>>> On Fri, May 24, 2019 at 8:34 AM John Kitchin <jkitchin@andrew.cmu.edu>
>>> wrote:
>>>
>>>> I still use this. Do you see any issues in the Messages?
>>>>
>>>> If you try attr_latex does it work? If not you may have an imagemagick
>>>> problem that can’t rescale the thumbnail. Note you will have to toggle
>>>> the
>>>> image display after you add that.
>>>>
>>>> On Fri, May 24, 2019 at 11:18 AM William Denton <wtd@pobox.com> wrote:
>>>>
>>>>> It used to be possible use ATTR_ORG on images to make them display at a
>>>>> different size, which was very useful when the images were large. It
>>>>> worked
>>>>> like this:
>>>>>
>>>>> #+ATTR_ORG: :width 300
>>>>> [[file:very-large-image.jpg]]
>>>>>
>>>>> I haven't needed it for a while, but today I went to use it and it's
>>>>> gone! I
>>>>> grepped the source code, ORG-NEWS and the git log, but didn't see any
>>>>> mention of
>>>>> it. What happened? Did it go in version 9? Am I overlooking
>>>>> something? I
>>>>> feel like I've stepped into some parallel universe where everything is
>>>>> the same
>>>>> except this one Org command.
>>>>>
>>>>> Bill
>>>>> --
>>>>> William Denton :: Toronto, Canada --- Listening to Art:
>>>>> https://listeningtoart.org/
>>>>> https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/
>>>>> Caveat lector. --- STAPLR: http://staplr.org/
>>>>>
>>>>> --
>>>> John
>>>>
>>>> -----------------------------------
>>>> Professor John Kitchin
>>>> Doherty Hall A207F
>>>> Department of Chemical Engineering
>>>> Carnegie Mellon University
>>>> Pittsburgh, PA 15213
>>>> 412-268-7803
>>>> @johnkitchin
>>>> http://kitchingroup.cheme.cmu.edu
>>>>
>>>>
>>
>
> --
> William Denton
> https://www.miskatonic.org/
> Librarian, artist and licensed private investigator.
> Toronto, Canada
--
William Denton
https://www.miskatonic.org/
Librarian, artist and licensed private investigator.
Toronto, Canada
prev parent reply other threads:[~2021-07-13 18:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 15:16 What happened to ATTR_ORG? William Denton
2019-05-24 15:31 ` John Kitchin
2019-05-25 0:54 ` steen
2019-05-25 4:12 ` Cheong Yiu Fung
2021-07-13 17:13 ` [O] " William Denton
2021-07-13 18:06 ` William Denton [this message]
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=alpine.DEB.2.22.394.2107131404360.58488@shell3.miskatonic.org \
--to=wtd@pobox.com \
--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).