From: Ralf Schmitt <ralf@brainbot.com>
Subject: Re: texexec command line switches missing in ruby version
Date: Wed, 27 Sep 2006 14:22:26 +0200 [thread overview]
Message-ID: <efdqe3$lrg$1@sea.gmane.org> (raw)
In-Reply-To: <E1GSY49-0000zw-00@skye.ra.phy.cam.ac.uk>
Sanjoy Mahajan wrote:
> I'm not sure if your command got mangled by the mailer disliking long
> lines, but it looks like you have this line:
>
> ralf@schrotti:~/tmp$ ~/texmf/scripts/context/ruby/texmfstart.rb texexec t.tex -- result bla.pdf
>
> i.e. something like "texexec t.tex -- result bla.pdf"
>
it was texexec t.tex --result bla.pdf (i.e. without the space between --
and result).
> The texexec man entry, I think for the perl version, says:
>
> --result=FILENAME
> Allows you to change the basename of the output
> file. See --mode for an example.
>
> And this command works:
>
> texexec t.tex --result=bla
>
same here. the equal sign was missing from my command line (the perl
version works without an equal sign).
> Although at the end it says:
>
> TeXExec | renaming t to bla
> TeXExec | restoring t
> TeXExec | fatal error No such file or directory - t.tuo
>
> Is the last line anything to worry about, perhaps in a more complex
> test file that needed the .tuo file?
>
> By the way, I use these two executable scripts to shorten the command
> lines:
>
> $ cat /home/sanjoy/bin/texmfstart
> #!/bin/bash
> ruby `kpsewhich --format=texmfscripts texmfstart.rb` "$@"
>
> $ cat /home/sanjoy/bin/texexec
> #!/bin/sh
> texmfstart texexec.rb "$@"
>
Thanks, I'm using them too, but I remember there was some confusion
about "$@" versus $@ in this command.
next prev parent reply other threads:[~2006-09-27 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 12:21 Ralf Schmitt
2006-09-26 12:29 ` Hans Hagen
2006-09-26 12:35 ` Ralf Schmitt
2006-09-26 16:29 ` Hans Hagen
2006-09-26 17:28 ` Peter Rolf
2006-09-27 4:02 ` Sanjoy Mahajan
2006-09-27 7:08 ` Ralf Schmitt
2006-09-27 11:59 ` Sanjoy Mahajan
2006-09-27 12:22 ` Ralf Schmitt [this message]
2006-09-27 12:39 ` Hans Hagen
2006-09-27 13:23 ` Sanjoy Mahajan
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='efdqe3$lrg$1@sea.gmane.org' \
--to=ralf@brainbot.com \
--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).