From: Hans Hagen <pragma@wxs.nl>
Subject: Re: texexec --mode=xxx --mode=yyy
Date: Tue, 16 Jan 2007 08:50:09 +0100 [thread overview]
Message-ID: <45AC83B1.2040707@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0701151852030.10596@gaston.pm>
� wrote:
> On Sun, 14 Jan 2007, Hans Hagen wrote:
>
>
>>> is it possible to make "texexec --mode=xxx --mode=yyy" behave the same as
>>> "texexec --mode=xxx,yyy" ?
>>>
>>> I need it, because I have a server that automatically generates pdf-files
>>> via "texexec --mode=xxx ..." and the rest of the command-line can be
>>> anything found in the tex-fileheader (for example another --mode=yyy).
>>>
>>>
>> setupmodes (and therefore the commandline option) does accent comma
>> separated lists
>>
>
> Hello Hans,
>
> the question is, if you could modify texexec to behave the same way, when
> used with these 2 command-lines:
> 1.) texexec --mode=xxx --mode=yyy file
> 2.) texexec --mode=xxx,yyy file
>
this will not happen soon since i dislike multiple same-name - options
> Imagine a command (an alias) my-texexec = "texexec --mode=xxx" that is used
> for example like this:
> my-texexec --mode=yyy file
> Then, the mode=xxx gets overwritten...
>
yeah, that shat i used it for -)
i can add support for modes to the ctx file feature (ctx files control
texexec)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2007-01-16 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 15:28 Peter Münster
2007-01-14 17:46 ` Hans Hagen
2007-01-15 17:56 ` Peter Münster
2007-01-16 7:50 ` Hans Hagen [this message]
2007-01-16 17:54 ` Peter Münster
2007-01-16 20:23 ` 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=45AC83B1.2040707@wxs.nl \
--to=pragma@wxs.nl \
--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).