From: Scott Schwartz <schwartz@groucho.cs.psu.edu>
To: rc@archone.tamu.edu
Subject: -x -n
Date: Sat, 4 Apr 1992 22:08:44 -0600 [thread overview]
Message-ID: <92Apr4.230853est.2538@groucho.cs.psu.edu> (raw)
This is wierd:
; rc -x -n
fn x {switch($status){case [^'~'^0]*;echo '# status' $status;}}
; ls
ls
It prints my prompt function, but only once, and without the correct
name.
One other wierdness... lists print as, e.g.,
path=((($minpath $miscpath) $nfspath) .)
That seems backwards to me. Wouldn't
path=($minpath ($miscpath ($nfspath .)))
be more aestetic?
next reply other threads:[~1992-04-05 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-04-05 4:08 Scott Schwartz [this message]
1992-04-05 4:56 Byron Rakitzis
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=92Apr4.230853est.2538@groucho.cs.psu.edu \
--to=schwartz@groucho.cs.psu.edu \
--cc=rc@archone.tamu.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).