sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: arnold@cc.gatech.edu (Arnold Robbins)
To: Scott Schwartz <schwartz@galapagos.cse.psu.edu>,
	Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
Cc: arnold@skeeve.atl.ga.us
Subject: Re: 9menu
Date: Tue, 29 Nov 1994 10:10:48 -0500	[thread overview]
Message-ID: <199411291510.KAA27318@penfold.cc.gatech.edu> (raw)
In-Reply-To: Scott Schwartz's 25-line message on Nov 28, 10:08pm

I sent the announcement to sam-fans since that seems to be where most
of the discussion of 9term takes place. I figured 9fans was more for
discussion of the real thing, not faking it under Unix.

As to this:

> To: Sam Fans <sam-fans@hawkwind.utcs.toronto.edu>
> Subject: 9menu
> Date: 	Mon, 28 Nov 1994 22:08:29 -0500
> From: Scott Schwartz <schwartz@galapagos.cse.psu.edu>
> 
> As long as we are being 9fans, how about this:
> 
> --- 1.1	1994/11/29 03:02:07
> +++ 9menu.c	1994/11/29 03:02:53
> @@ -228,7 +228,7 @@
>  		return;
>  
>  	close(ConnectionNumber(dpy));
> -	execl("/bin/sh", "sh", "-c", com, NULL);
> +	execl("/bin/rc", "rc", "-c", com, NULL);
>  	_exit(1);
>  }

That's not unreasonable, what I should probably do is fix 9menu to
just use ${SHELL:-/bin/sh}. If I find some spare time I'll probably
do that.  If someone wishes to beat me to it and mail me a patch,
that's fine too.

Arnold


             reply	other threads:[~1994-11-29 15:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1994-11-29 15:10 Arnold Robbins [this message]
1994-11-29 16:10 ` 9menu Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
1994-11-30 15:59 9menu Arnold Robbins
1994-11-29 17:10 9menu rob
1994-11-30  1:22 ` 9menu Scott Schwartz
1994-11-29 17:09 9menu Arnold Robbins
1994-11-29 15:32 9menu Arnold Robbins
1994-11-29  3:08 9menu 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=199411291510.KAA27318@penfold.cc.gatech.edu \
    --to=arnold@cc.gatech.edu \
    --cc=arnold@skeeve.atl.ga.us \
    --cc=sam-fans@hawkwind.utcs.toronto.edu \
    --cc=schwartz@galapagos.cse.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).