From: Byron Rakitzis <byron>
To: rc, schwartz@groucho.cs.psu.edu
Subject: Re: -x -n
Date: Sat, 4 Apr 1992 22:56:05 -0600 [thread overview]
Message-ID: <92Apr4.225613cst.45317@archone.tamu.edu> (raw)
Well, the prompt part is your prompt function getting imported from the
environment & interpreted by the rc parser. Since this happens only
once (and a good thing!) you only see it once. The "wrong name" is just
a convenient trick used to munge the environment string into something
the parser will recognize.
I suppose it is debatable whether rc -n should be interpreting fn
prompt at all---I hadn't thought of this up to now and offhand I
should say the answer is no. I will fix this.
Lists are parsed "backwards" because of yacc. Doing it the other way
would consume yacc stack space proportional to the length of the list.
Anyone up for writing a recursive-descent parser for rc? (just
kidding...)
next reply other threads:[~1992-04-05 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-04-05 4:56 Byron Rakitzis [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-04-05 4:08 Scott Schwartz
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.225613cst.45317@archone.tamu.edu \
--to=schwartz@groucho.cs.psu.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).