rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Brendan Kehoe <brendan@cs.widener.edu>
To: byron@archone.tamu.edu
Cc: rc@archone.tamu.edu
Subject: first impressions rc 1.3beta
Date: Fri, 7 Feb 1992 14:23:08 -0600	[thread overview]
Message-ID: <199202072023.AA21539@ashley.cs.widener.edu> (raw)
In-Reply-To: Byron Rakitzis's message of Fri, 7 Feb 1992 08:57:21 -0600 <92Feb7.085728cst.45332@archone.tamu.edu>


   From: Byron Rakitzis <byron@archone.tamu.edu>
   Date: Fri, 7 Feb 1992 08:57:21 -0600

   Re: bison. bison generates a larger file than old Berkeley yacc, my
   reference point. Now, this is starting to look like useless
   information, since no one seems to be running the old yacc! (NeXT
   does---I'll keep using it as long as I can for ALL my rc builds). I'll
   take the comment out.

Since you bring it up (and I figure a bunch of people reading this
right now have a good amount of experience with 'em--more than I, at
least), I'm going to take a quick liberty...

I'm putting together a reference card (same format as the GNU emacs
refcard) for Bison & Flex; if any of you have suggestions on what
information would be really good to have on such a thing, I'd love to
hear them.

We return you to your regularly scheduled beta test.  This message
will self-destruct in ten seconds.

--
Brendan Kehoe, Sun Network Manager                      brendan@cs.widener.edu
Widener University                                                 Chester, PA

            This is the .signature that Bell Atlantic doesn't want you to see.


  reply	other threads:[~1992-02-07 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-07 14:57 Byron Rakitzis
1992-02-07 20:23 ` Brendan Kehoe [this message]
  -- strict thread matches above, loose matches on Subject: below --
1992-02-08 16:38 Byron Rakitzis
1992-02-08 15:58 malte
1992-02-08 15:44 malte
1992-02-07 13:39 malte
1992-02-07 13:53 ` Robert van Liere
1992-02-07 20:21   ` 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=199202072023.AA21539@ashley.cs.widener.edu \
    --to=brendan@cs.widener.edu \
    --cc=byron@archone.tamu.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).