ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: wrong patch
Date: Wed, 2 Jun 2004 19:50:28 +0200	[thread overview]
Message-ID: <557374B2-B4BD-11D8-BE51-0030659899AA@fiee.net> (raw)
In-Reply-To: <6.1.1.1.2.20040602100854.01b9bec0@server-1>


Am Mittwoch, 02.06.04, um 10:09 Uhr (Europe/Zurich) schrieb Hans Hagen:
>> >     if ($ENV["TEMP"] && -e $ENV["TEMP"]) {
>> >         $RunPath = $ENV["TEMP"] ;
>> >     } elsif ($ENV["TMP"] && -e $ENV["TMP"]) {
>> >         $RunPath = $ENV["TMP"] ;
>> >     }
> interestingly perl does not complain, which is one more reason to go 
> ruby

Do you
use warnings;
use strict;
?



Grüßlis vom Hraban!
-- 
http://www.fiee.net/texnique/

  reply	other threads:[~2004-06-02 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 19:19 Hans Hagen
2004-06-01 21:33 ` Nikolai Weibull
2004-06-02  8:09   ` Hans Hagen
2004-06-02 17:50     ` Henning Hraban Ramm [this message]
2004-08-12  8:44     ` Christopher Creutzig

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=557374B2-B4BD-11D8-BE51-0030659899AA@fiee.net \
    --to=hraban@fiee.net \
    --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).