From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Nick Dokos <ndokos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Live refresh of inline images with org-display-inline-images stopped working
Date: Thu, 22 Jan 2015 14:34:49 +0100 [thread overview]
Message-ID: <86lhkvuefa.fsf_-_@example.com> (raw)
In-Reply-To: <8761ip5rml.fsf-/Z0n3E7Cx4sTdff2QS34phcY2uh10dtjAL8bYrjMMd8@public.gmane.org> (Nick Dokos's message of "Tue, 22 Jul 2014 11:40:18 -0400")
Nick Dokos wrote:
> Brett Viren <bv-IGkKxAqZmp0@public.gmane.org> writes:
>> Nick Dokos <ndokos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>>
>>> I think you'd be better off with the tip that Rick Frankel posted in
>>> the same thread:
>>>
>>> #+BEGIN_SRC emacs-lisp
>>> (add-hook 'org-babel-after-execute-hook
>>> (lambda () (org-display-inline-images nil t)))
>>> #+END_SRC
>>
>> Thanks Nick (and Rick). I changed this to use the "re" version:
>>
>> #+BEGIN_SRC emacs-lisp
>> (add-hook 'org-babel-after-execute-hook
>> (lambda () (org-redisplay-inline-images)))
>> #+END_SRC
>>
>> and it works great!
>
> It should work with the non-"re" version as well (and it is more
> efficient that way - particularly if you call it with refresh == t).
As experienced by wdkmls [1], I noticed that the non-"re" version
stopped working -- preferred as it was the most efficient one.
OTOH, the "re" version does work as expected.
Best regards,
Seb
[1] http://emacs.stackexchange.com/questions/3302/live-refresh-of-inline-images-with-org-display-inline-images
--
Sebastien Vauban
prev parent reply other threads:[~2015-01-22 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 22:12 org-redisplay-inline-images and export to HTML Brett Viren
2014-07-21 23:17 ` Nick Dokos
2014-07-22 13:57 ` Brett Viren
2014-07-22 15:40 ` Nick Dokos
[not found] ` <8761ip5rml.fsf-/Z0n3E7Cx4sTdff2QS34phcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2015-01-22 13:34 ` Sebastien Vauban [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=86lhkvuefa.fsf_-_@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
--cc=ndokos-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).