emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Julian M. Burgos" <julian.burgos@hafogvatn.is>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
	"Doyley, Marvin M." <m.doyley@rochester.edu>
Subject: Re: Viewing pdf images
Date: Wed, 05 Apr 2017 11:52:08 +0000	[thread overview]
Message-ID: <CAFyQvY19ByUmjXQijTJ3TOkwgGZX1yunxhWnNTBzctUfihRzMg@mail.gmail.com> (raw)
In-Reply-To: <xgz1st75hx9.fsf@hafogvatn.is>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Wed, Apr 5, 2017, 5:21 AM Julian M. Burgos <julian.burgos@hafogvatn.is>
wrote:

> Can you clarify the purpose of this function?  I understand that
> produces an image of each pdf linked to the file.


That's correct, but the user can control when that happens by adding that
function to the appropriate hook.

 But

the question in
> emacs.stackexchange was about displaying pdf's as inline images.


Yes, I forgot to change the hook when I updated the whole answer; I have
fixed that now. Now the answer shows how to add this function to the
before-save-hook.

 Your

function only converts the pdfs into images (and you have to do an
> export to achieve that).


Well, the function org-include-img-from-pdf is the workhorse here, and it
doesn't depend on when you want the PDF to PNG conversion to happen. The
"when" depends on the hook you add the function to.

  You would still would have to add a link to
> the image file in order to see it as an inline image.
> add a link in order to see it, correct?
>

I didn't follow that. The user is already adding that. Example:

# ()convertfrompdf:t
# User needs to have a ./foo.pdf. That will be converted to the below
referenced foo.png.
[[./foo.png]]

When I get to a computer, I'll confirm if the #+CAPTION: and/or #+NAME: is
needed for the inline images to show. Above works fine for exports, so I
assumed that the inline images should show fine too.



-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 3093 bytes --]

  reply	other threads:[~2017-04-05 11:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 12:27 Viewing pdf images Doyley, Marvin M.
     [not found] ` <52f1d2ee-b964-39ac-3c96-674ad7b6137e@yahoo.com>
2017-03-17 13:48   ` Doyley, Marvin M.
2017-03-21 10:34     ` Julian M. Burgos
2017-03-22  0:22       ` Doyley, Marvin M.
2017-04-05  3:22         ` Kaushal Modi
2017-04-05  9:21           ` Julian M. Burgos
2017-04-05 11:52             ` Kaushal Modi [this message]
2017-04-05 15:23               ` Kaushal Modi
2017-04-06 15:02               ` Julian M. Burgos
2017-04-09 22:06 ` Eduardo Mercovich
2017-04-10  0:00   ` Doyley, Marvin M.
2017-04-10 16:51     ` Eduardo Mercovich
2017-04-12 13:05       ` Doyley, Marvin M.
     [not found]     ` <c8efd5b805e447aba02e063b2f4b5327@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2017-04-10 17:06       ` Eric S Fraga

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=CAFyQvY19ByUmjXQijTJ3TOkwgGZX1yunxhWnNTBzctUfihRzMg@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=julian.burgos@hafogvatn.is \
    --cc=m.doyley@rochester.edu \
    /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).