From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: Dash equivalent of $BASH_SOURCE (for setuptex)
Date: Thu, 22 Nov 2012 10:21:28 +0100 [thread overview]
Message-ID: <50ADEE98.5000706@elvenkind.com> (raw)
In-Reply-To: <50ADEDF5.9000409@wxs.nl>
On 11/22/2012 10:18 AM, Hans Hagen wrote:
> On 11/21/2012 8:28 PM, Peter Münster wrote:
>> On Wed, Nov 21 2012, Mojca Miklavec wrote:
>>
>>> But Peter's idea is also not that bad. The drawback is that the
>>> distribution cannot be moved to a different directory then, but one
>>> could also have combination of both approaches somehow.
>>
>> Is it worth the trouble to keep setuptex?
>> Just saying "Please add ... to your PATH" should be enough IMO.
>
> I often use it.
Me too, I have quite a bunch of scripts that are distributed to
online servers that do not all have the same architecture.
Best wishes,
Taco
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-11-22 9:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 11:56 Mojca Miklavec
2012-11-21 17:35 ` Alan BRASLAU
2012-11-21 18:45 ` Mojca Miklavec
2012-11-21 19:28 ` Peter Münster
2012-11-21 21:05 ` Mojca Miklavec
2012-11-22 9:18 ` Hans Hagen
2012-11-22 9:21 ` Taco Hoekwater [this message]
2012-11-22 9:39 ` Alan BRASLAU
2012-11-21 18:12 ` Peter Münster
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=50ADEE98.5000706@elvenkind.com \
--to=taco@elvenkind.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).