From: Nick Dokos <nicholas.dokos@hp.com>
To: Richard Stanton <stanton@haas.berkeley.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Subject: Re: Problem exporting to PDF (and viewing)
Date: Fri, 18 May 2012 18:19:33 -0400 [thread overview]
Message-ID: <13715.1337379573@alphaville> (raw)
In-Reply-To: Message from Richard Stanton <stanton@haas.berkeley.edu> of "Fri, 18 May 2012 13:56:19 PDT." <40C7B1BFC291ED4E9D10436D07736A33470478BC1E@EXMAIL7.haas.uc.berkeley.edu>
Richard Stanton <stanton@haas.berkeley.edu> wrote:
> > > 2) If not, where is the code that interprets %s? I can try stepping
> > > through it and see what I can find.
> > >
> >
> > It happens in org.el:org-open-file, specifically this piece of the code (I think):
> >
> > ,----
> > | (while (string-match "%s" cmd)
> > | (setq cmd (replace-match
> > | (save-match-data
> > | (shell-quote-argument
> > | (convert-standard-filename file)))
> > | t t cmd)))
> > `----
>
> I did some tracing through, and have found where things go wrong.
>
> At the start of the code listed above,
>
> cmd = "c:/progra~1/sumatrapdf/sumatrapdf.exe %s"
> file = "c:/dropbox/org/personal.pdf"
>
> (convert-standard-filename file) returns
> "C:/dropbox/org/personal.pdf"
>
> So far so good...
>
> However,
>
> (shell-quote-argument (convert-standard-filename file)) returns
> "c\\:dropbox/org/personal.pdf"
>
> That's where the problem occurs. After this block of code is completed, cmd takes the value
> "c:/progra~1/sumatrapdf/sumatrapdf.exe c\\:dropbox/org/personal.pdf"
>
> This command causes sumatrapdf to squawk with an error. It's the "\\:" that causes the problem. If, after this block of code executes, I manually switch the "\\:" back to ":/", so cmd goes back to
>
> "c:/progra~1/sumatrapdf/sumatrapdf.exe c:/dropbox/org/personal.pdf"
>
> and then press "c" to continue, the PDF file pops up just fine. Could we just drop the call to shell-quote-argument? It seems like everything would work fine without this call.
>
Can you trace the execution of shell-quote-argument? In particular, what is the
value of system-type and what result do you get when you evaluate the form
(w32-shell-dos-semantics)
?
It seems that it falls through to the default case and I'm not sure
it should.
Nick
next prev parent reply other threads:[~2012-05-18 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-12 4:10 Problem exporting to PDF (and viewing) Richard Stanton
2012-05-12 14:23 ` Jonathan Leech-Pepin
2012-05-12 14:39 ` Nick Dokos
2012-05-13 4:05 ` Richard Stanton
2012-05-13 4:53 ` Nick Dokos
2012-05-18 20:56 ` Richard Stanton
2012-05-18 21:11 ` Nick Dokos
2012-05-18 21:45 ` Richard Stanton
2012-05-18 22:19 ` Nick Dokos [this message]
2012-05-18 23:30 ` Richard Stanton
2012-05-19 7:07 ` Achim Gratz
2012-05-13 6:00 ` Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2012-05-14 5:33 Richard Stanton
2012-05-11 23:52 Richard Stanton
2012-05-12 7:22 ` Jude DaShiell
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=13715.1337379573@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=stanton@haas.berkeley.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).