Bug#482999: The behavior of `jobs -p` is definitely, without a doubt, a bug

2016-05-18 Thread Geoff Nixon
On Wed, 18 May 2016 14:03:59 -0700 Harald van Dijk <har...@gigawatt.nl> wrote > Hi, > > On 13/05/16 04:06, Geoff Nixon wrote: > > Let me start with a couple of corrections to that previous thread. > > > > > > 1. The line: jobs -p

Bug#482999: The behavior of `jobs -p` is definitely, without a doubt, a bug

2016-05-12 Thread Geoff Nixon
d to emulate the same behavior. But I couldn't find (and I doubt there is) a way to do it without at lease something non-POSX, like a ksh DEBUG trap. And finally, do I really need to lay out the reasons why one might need the ability to list *all* jobs, as opposed to simply the last one used? To me,