From: Carsten Dominik <carsten.dominik@gmail.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-publish: docview all pdf files
Date: Tue, 24 Sep 2013 15:13:49 +0200 [thread overview]
Message-ID: <3F6E568B-7065-4052-AE8E-857C24BF2921@gmail.com> (raw)
In-Reply-To: <20130607161516.GA19084@panahar>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
Hi Vikas,
maybe you could make me a minimal setup so that I can reproduce this?
Just a little folder with two files and a minimal .emacs that defines
publishing of these files to some other directory.
That would be useful.
- Carsten
On 7.6.2013, at 18:15, Vikas Rawal <vikaslists@agrarianresearch.org> wrote:
> When I publish the project, orgmode attempts to open all pdf files
> (which are static content). It seems to me that some sort of indexing
> is being attempted though I am not sure. I think it started happening
> after I included creation of a sitemap.
>
> I get messages like this:
>
> DocView: process pdf/ps->png changed status to killed.
>
> This slows down publishing considerably. I have just added some large
> pdf files, and now it asks me for each such file whether I want to
> open it. org-publish gets stuck if I say yes, and aborts publishing if
> I say no.
>
> Is there a way, I could tell orgmode to not try to process these pdf
> files. pdf files are being processed through a sub-project that deals
> with static content (org-publish-attachment).
>
> Would be grateful for any advice.
>
> Best,
>
> Vikas
>
>
>
>
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2013-09-24 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 16:15 org-publish: docview all pdf files Vikas Rawal
2013-09-24 13:13 ` Carsten Dominik [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=3F6E568B-7065-4052-AE8E-857C24BF2921@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=vikaslists@agrarianresearch.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).