rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: broman@Np.nosc.mil (Vincent Broman)
To: culliton@srg.srg.af.mil
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Re: Signal weirdness
Date: Mon, 14 Mar 1994 19:12:20 -0500	[thread overview]
Message-ID: <9403150012.AA00697@Np.nosc.mil> (raw)
In-Reply-To: <9403141813.aa13127@ceres.srg.af.mil> (culliton@srg.srg.af.mil)

I get the symptom you describe with my rc1.4 + readline
on sunos4.1.3 .

Vincent Broman,  code 572 Bayside                        Phone: +1 619 553 1641
Naval Command Control and Ocean Surveillance Center, RDT&E Div.
San Diego, CA  92152-6147,  USA                          Email: broman@nosc.mil


  reply	other threads:[~1994-03-15  0:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-03-14 23:13 Tom Culliton x2278
1994-03-15  0:12 ` Vincent Broman [this message]
  -- strict thread matches above, loose matches on Subject: below --
1994-03-15 15:15 Alan Watson
1994-03-15 10:52 malte
1994-03-14 21:46 Byron Rakitzis
1994-03-14 20:17 Tom Culliton x2278
1994-03-14 20:52 ` Chris Siebenmann

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=9403150012.AA00697@Np.nosc.mil \
    --to=broman@np.nosc.mil \
    --cc=broman@nosc.mil \
    --cc=culliton@srg.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).