From: Byron Rakitzis <byron>
To: rc
Subject: Re: Bug or feature?
Date: Mon, 19 Aug 1991 09:30:29 -0500 [thread overview]
Message-ID: <91Aug19.093039cdt.22540@archone.tamu.edu> (raw)
> From: malte@techfak.uni-bielefeld.de
> To: rc@archone.tamu.edu
> Subject: Bug or feature?
>
> I was just playing around with rc (1.1gamma) and discovered this (strange?)
> behaviour:
>
> 1) If I define a function fn like "fn fn { printenv | grep '^fn_' }"
> the output is always nothing and it is impossible to define a new
> function, because fn now has a different meaning. Bug or feature?
This is not right: fn alone is a keyword parsed by the parser as a
"delete function" command. When you type
; fn
to rc, you are saying "please delete these functions: (no arguments)". Now,
you are free to delete the above definition with
; fn fn
or even to define a new function
; fn foo { echo hi }
; foo
hi
;
I don't see how it's "impossible to define a new function". Is your rc
behaving that way? If so, it's broken and needs to be fixed..
> 2) Why doesn't this work:
> fn prompt { if(~ ($status) 1 2 3){
> prompt=('err ' '>> ')
> } else prompt=('ok ' '>> ')}
> I want the prompt to show "err " if the last command returned 1,2 or 3,
> else "ok ".
This works on my machine. Could you please send me a more detailed bug
report? I'll try to fix anything that's wrong...
next reply other threads:[~1991-08-19 14:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1991-08-19 14:30 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1991-08-19 15:03 malte
1991-08-19 11:22 malte
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=91Aug19.093039cdt.22540@archone.tamu.edu \
--to=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).