ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Changes for setuptex
Date: Tue, 15 Mar 2011 12:18:27 +0100	[thread overview]
Message-ID: <AANLkTik3R_BMbo-nU_FARH5KkcP_L=P+nuoqMJ3yTXEV@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimk7vPnb9ZNb2uQ_0dcxNw=q1OfT1ktdRVan6CX@mail.gmail.com>

Dear Cecil,

I would be glad to fix the script, but may I only ask for some simple
explanation of what your code does? (I hardly know bash.)

Mojca


On Tue, Mar 15, 2011 at 10:50, Cecil Westerhof <cldwesterhof@gmail.com> wrote:
> To make the shell script setuptex more robust I would add at the beginning:
> set -o errexit
> set -o nounset
>
> function isVarSet() {
>   if [[ ${#} -ne 1 ]] ; then
>     fatal "${FUNCNAME} <VARIABLE-NAME>"
>     return
>   fi
>
>   declare -p ${1} &>/dev/null
>   return
> }
>
> And use:
>     if  ! isVarSet PS1  ; then
> instead of:
>     if [ "x$PS1" != "x" ] ; then
>
> I use in my script that calls setuptex
> set -o errexit
> set -o nounset
>
> and that breaks the script. With my change there is no problem.
___________________________________________________________________________________
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
___________________________________________________________________________________

      reply	other threads:[~2011-03-15 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  9:50 Cecil Westerhof
2011-03-15 11:18 ` Mojca Miklavec [this message]

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='AANLkTik3R_BMbo-nU_FARH5KkcP_L=P+nuoqMJ3yTXEV@mail.gmail.com' \
    --to=mojca.miklavec.lists@gmail.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).