zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: Bogus "no such job" (Re: Preliminary release of 3.0.8 - please test)
Date: 10 Mar 2000 10:52:50 GMT	[thread overview]
Message-ID: <slrn8chl02.3fn.mason@coral.primenet.com.au> (raw)
In-Reply-To: <200003100933.KAA03375@beta.informatik.hu-berlin.de>

Sven Wischnowsky <wischnow@informatik.hu-berlin.de> typed:
:Geoff, do you remember what you did before you got that message? Did
:you kill some job/process? What (kind of) commands did you suspend?
:Pipes with lists in them, commands that do some kind of signal
:handling? (Yes, I'm guessing wildly...)

Job 2 was vim; job 1 was make (BSD make ~= pmake) or maybe another
vim job.  I've got no memory of running a third job, though it may
have been something like ``cvs log <somefile> | less'' or
``cvs status |& fgrep Status | fgrep -v Up-to''.  I'm sure I never
had four jobs going.  Unfortunately I didn't attach a debugger or
core dump it so I have no ability to query values from it in that
state.  It's very rare (obviously) though I've either got deja vu
or I've seen it before at least once (and it would have been quite
a while ago (a year? more maybe) so I suspect it's not from any
recent changes).

Regards,
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874


  reply	other threads:[~2000-03-10 10:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-10  9:33 Sven Wischnowsky
2000-03-10 10:52 ` Geoff Wing [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-09 12:01 Sven Wischnowsky
2000-02-29 10:33 Preliminary release of 3.0.8 - please test Geoff Wing
2000-02-29 16:18 ` Bart Schaefer
2000-03-03  2:55   ` Geoff Wing
2000-03-08  7:30     ` Bogus "no such job" (Re: Preliminary release of 3.0.8 - please test) 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=slrn8chl02.3fn.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --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).