rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Decklin Foster <fosterd@hartwick.edu>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: rc error messages from scripts
Date: Thu, 9 Dec 1999 08:59:24 -0500	[thread overview]
Message-ID: <19991209085924.A1882@debian> (raw)
In-Reply-To: <199912090829.AAA23488@peanut.rakitzis.com>; from byron@rakitzis.com on Thu, Dec 09, 1999 at 12:29:59AM -0800

Byron Rakitzis writes:

> Also: in general, child processes in the foreground do not need to be
> identified by their pid. It's redundant.

Ah. silly me. How about changing the other messages and leaving
'segmentation fault' as a special case (ie, no argv[0])? would you
welcome such a patch?

-- 
Decklin
Written with Debian GNU/Linux - http://www.debian.org/


       reply	other threads:[~1999-12-09 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199912090829.AAA23488@peanut.rakitzis.com>
1999-12-09 13:59 ` Decklin Foster [this message]
1999-12-10  7:40 Byron Rakitzis
  -- strict thread matches above, loose matches on Subject: below --
1999-12-09  8:10 Byron Rakitzis
1999-12-08 15:09 Bengt Kleberg
1999-12-09  7:37 ` Decklin Foster

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=19991209085924.A1882@debian \
    --to=fosterd@hartwick.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --subject='Re: rc error messages from scripts' \
    /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

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).