From: Robert Ullrey <ullreyr@scc.losrios.edu>
Subject: texexec in a shell script
Date: Mon, 18 Apr 2005 15:28:01 -0700 [thread overview]
Message-ID: <46190acd4e027c8cc4517ca8db577aaa@scc.losrios.edu> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 521 bytes --]
I know someone out there has the answer to this. If I run texexec
through a shell, even with the full path to texexec, I get an error,
"/usr/local/teTeX/bin/powerpc-apple-darwin-current/texexec: line 1:
sed: command not found
`.pl' not found."
Running Google with the error shows that it is quit common, but I could
not find a good fix. I guess kpsewhich gets lost in the shell because
the shell needs full paths the whole way through the command. Has
anyone written a shell to get texexec --pdf ?
Thanks
Robert
[-- Attachment #1.2: Type: text/enriched, Size: 618 bytes --]
I know someone out there has the answer to this. If I run texexec
through a shell, even with the full path to texexec, I get an error,
"<italic><x-tad-smaller>/usr/local/teTeX/bin/powerpc-apple-darwin-current/texexec:
line 1: sed: command not found
`.pl' not found."
</x-tad-smaller></italic>Running Google with the error shows that it
is quit common, but I could not find a good fix. I guess kpsewhich
gets lost in the shell because the shell needs full paths the whole
way through the command. Has anyone written a shell to get texexec
--pdf ?
Thanks
Robert
<italic><x-tad-smaller>
</x-tad-smaller></italic>
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2005-04-18 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 22:28 Robert Ullrey [this message]
2005-04-19 7:39 ` Hans Hagen
2005-04-19 7:55 ` Taco Hoekwater
2005-04-19 8:42 ` Adam Lindsay
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=46190acd4e027c8cc4517ca8db577aaa@scc.losrios.edu \
--to=ullreyr@scc.losrios.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).