From: culliton@srg.af.mil (Tom Culliton x2278)
To: rc@hawkwind.utcs.toronto.edu
Subject: An extra patch for trip.rc
Date: Thu, 13 May 1993 14:07:23 -0400 [thread overview]
Message-ID: <9305131407.aa20335@ceres.srg.af.mil> (raw)
Just to make life a bit easier here is the patch to trip.rc which fixes
the "~! should be !~" bug.
Tom
----------8<--------------------CUT HERE--------------------8<----------
*** trip.rc Wed Apr 21 19:10:23 1993
--- trip.rc2 Wed Apr 21 18:29:53 1993
***************
*** 237,243 ****
if (~ `{echo -n} ?)
fail echo -n
! if (~! `` '' {echo --} $nl)
fail echo --
pwd=`/bin/pwd cdpath=/ { # some local assignments
--- 237,243 ----
if (~ `{echo -n} ?)
fail echo -n
! if (!~ `` '' {echo --} $nl)
fail echo --
pwd=`/bin/pwd cdpath=/ { # some local assignments
***************
*** 409,415 ****
echo hi
eof
! prompt=';' if (~! `` '' {. -i /tmp/dot.$pid>[2=1]} ';hi'^$nl';')
fail dot -i
submatch .' '/tmp/dot.$pid hi dot
--- 409,415 ----
echo hi
eof
! prompt=';' if (!~ `` '' {. -i /tmp/dot.$pid>[2=1]} ';hi'^$nl';')
fail dot -i
submatch .' '/tmp/dot.$pid hi dot
***************
*** 457,463 ****
~ $* bar || fail restore of '$*' after local group
~ `{exec>[2=1];$rc -xc 'foo=()'} 'foo=()' || fail -x echo of variable deletion
! fn_ff='{' prompt='' if (~! `` $nl {$rc -cff>[2=1]} 'line 1: '*' error near eof')
fail 'bogus function in environment'
#
--- 457,463 ----
~ $* bar || fail restore of '$*' after local group
~ `{exec>[2=1];$rc -xc 'foo=()'} 'foo=()' || fail -x echo of variable deletion
! fn_ff='{' prompt='' if (!~ `` $nl {$rc -cff>[2=1]} 'line 1: '*' error near eof')
fail 'bogus function in environment'
#
***************
*** 517,523 ****
#
fn prompt {echo hi}
! prompt=() if (~! `{$rc -i /dev/null>[2]/dev/null} hi) fail fn prompt
fn prompt
#
--- 517,523 ----
#
fn prompt {echo hi}
! prompt=() if (!~ `{$rc -i /dev/null>[2]/dev/null} hi) fail fn prompt
fn prompt
#
reply other threads:[~1993-05-13 18:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9305131407.aa20335@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).