zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: "sh" job control
Date: Thu, 30 Sep 1999 16:44:01 +0200	[thread overview]
Message-ID: <9909301444.AA15947@ibmth.df.unipi.it> (raw)
In-Reply-To: "Zefram"'s message of "Thu, 30 Sep 1999 15:53:06 DFT." <E11WhZy-00015a-00@crucigera.fysh.org>

Zefram wrote:
> Peter Stephenson wrote:
> >Clint Adams wrote:
> >> The following patch introduces an option "shjobcontrol" (bad name?)
> >> which skips the checkjobs() call.
> 
> I think CHECK_JOBS (with the opposite sense) would be a better name.

That would mean it has the same sense as HUP, which is logical.

> >It's probably because zsh doesn't set nohup by default. As it's set
> >by default in sh mode, this seems a reasonable combination.
> 
> What does POSIX say about it?

I can't see anything in the Single UNIX Specification, anyway.  The nohup
description refers to the sh description, but doesn't seem to specify it
one way or another.

By the way, looking at the standard, I discovered the following are
supposed to work.

% echo $(
echo # a comment)
)
% echo $(
cat <<\eof
a here doc with )
eof
)

That would basically mean recursively parsing the $(...) straight away,
which could be quite a lot of work.  I'm delighted to find it doesn't work
with HPUX 10.20's POSIX sh, either.

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


  reply	other threads:[~1999-09-30 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-30 14:24 Clint Adams
1999-09-30 14:08 ` Peter Stephenson
1999-09-30 14:53   ` Zefram
1999-09-30 14:44     ` Peter Stephenson [this message]
1999-09-30 15:27       ` Clint Adams
1999-09-30 14:57         ` Peter Stephenson
1999-09-30 15:07     ` Clint Adams
1999-10-01  1:41       ` POSIX (Was: PATCH: "sh" job control) Geoff Wing
1999-10-01  6:23         ` Bart Schaefer

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=9909301444.AA15947@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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