From: Aditya Mahajan <adityam@umich.edu>
Subject: texmfstart not recognizing $page
Date: Mon, 30 Oct 2006 15:53:33 -0500 (EST) [thread overview]
Message-ID: <Pine.WNT.4.63.0610301539340.3184@nqvgln> (raw)
Hi Hans,
In the latest beta
texmfstart --page=1 --file=metafun-p.pdf
does not work. This is the verbose output
texmfstart version 2.0.0
locating 'metafun-p.pdf' in current path '.'
locating 'metafun-p.pdf' in caller path 'f:/Research/Feedback/AC'
kpse : direct (forced)
using 'kpsewhich' to locate 'metafun-p' in suffix space 'pdf' (2)
checking E:\isoimage\usr\local\context\tex\texmf-mswin\BIN for
metafun-p
checking E:\isoimage\usr\local\context\bin for metafun-p
checking E:\Ruby\bin for metafun-p
checking E:\Python24\ for metafun-p
checking E:\Perl\bin for metafun-p
checking E:\Program Files\R\R-2.3.1\bin for metafun-p
checking E:\bin for metafun-p
checking for metafun-p
checking E:\Vim\vim70 for metafun-p
aggressively locating 'metafun-p' in document trees
locating 'metafun-p' in document tree
'e:/isoimage/usr/local/context/doc*'
registering 'metafun-p' as
'e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf'
registering 'THREAD' as
'e:/isoimage/usr/local/context/docroot/documents/general/manuals'
starting metafun-p.pdf
using 'system' call:
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
using 'system' call: pdfopen --page --file
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
using 'system' call: acroread
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
Even the simple
texmfstart metafun-p.pdf
fails with
texmfstart version 2.0.0
locating 'metafun-p.pdf' in current path '.'
locating 'metafun-p.pdf' in caller path 'f:/Research/Feedback/AC'
kpse : direct (forced)
using 'kpsewhich' to locate 'metafun-p' in suffix space 'pdf' (2)
checking E:\isoimage\usr\local\context\tex\texmf-mswin\BIN for
metafun-p
checking E:\isoimage\usr\local\context\bin for metafun-p
checking E:\Ruby\bin for metafun-p
checking E:\Python24\ for metafun-p
checking E:\Perl\bin for metafun-p
checking E:\Program Files\R\R-2.3.1\bin for metafun-p
checking E:\bin for metafun-p
checking for metafun-p
checking E:\Vim\vim70 for metafun-p
aggressively locating 'metafun-p' in document trees
locating 'metafun-p' in document tree
'e:/isoimage/usr/local/context/doc*'
registering 'metafun-p' as
'e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf'
registering 'THREAD' as
'e:/isoimage/usr/local/context/docroot/documents/general/manuals'
starting metafun-p.pdf
using 'system' call:
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
using 'system' call: pdfopen --page --file
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
using 'system' call: acroread
e:/isoimage/usr/local/context/docroot/documents/general/manuals/metafun-p.pdf
The first system call fails since ruby uses "/" rather than "\" as the
directory separator and windows does not like that.
The second system call fails since $page is '' (I don't know why). A
pdfopen --page --file filename
always fails.
The third system call fails since acroread is not present.
I fail to understand why $page is expanding to '' rather than 2 (or 0
in the second case).
Aditya
next reply other threads:[~2006-10-30 20:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 20:53 Aditya Mahajan [this message]
2006-10-30 23:11 ` Hans Hagen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.63.0610301539340.3184@nqvgln \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).