zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh workers <zsh-workers@sunsite.dk>
Subject: Re: zsh: Strange feature with 'jobs' commmand
Date: Thu, 30 May 2002 08:44:12 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0205300708110.3617-100000@ns1.sodaware.com> (raw)
In-Reply-To: <E17DPx8-00067B-00@bimbo.logica.co.uk>

On Thu, 30 May 2002, Oliver Kiddle wrote:

> Tricks like jobs > >(cat -) sort-of work so I was thinking a special
> case hack for jobs might not need a big rewrite. But I've never gone
> near that part of zsh's code so wouldn't know.

jobs >>(cat) works because >>(...) forces cat into a subshell, leaving
jobs in the foreground.  That's an entirely different flow of control.

It's relatively easy to add a new `cl' arg value to entersubsh() as a flag
when the command to be executed is the `jobs' builtin, to leave the job
table un-erased.  However, the code that does the traversing/printing of
the job table is littered with tests to silence it when the process is not
the foreground shell -- it's be really tricky to make `jobs' do something
useful while still preventing `bg' and `fg' from doing something broken.


  reply	other threads:[~2002-05-30 15:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.SV4.4.44.0205301632500.21658-100000@itsrm2.mow.siemens.ru>
2002-05-30 13:26 ` Oliver Kiddle
2002-05-30 15:44   ` Bart Schaefer [this message]
2002-05-30 15:48     ` Bart Schaefer
     [not found] <20020530135450.A16761@licia.dtek.chalmers.se>
2002-05-30 15:19 ` Peter Stephenson
2002-05-30 16:13   ` Oliver Kiddle
2002-05-30 17:22     ` Peter Stephenson
2002-06-05 14:55       ` Peter Stephenson
2002-06-06  5:45         ` Clint Adams
2002-06-06  9:25           ` Peter Stephenson

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=Pine.LNX.4.44.0205300708110.3617-100000@ns1.sodaware.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.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).