The behaviour on bash 4.2.53(1)-release seems to be different. For
example
$ ./history | his
bash: his: command not found...
[ Here I press enter to get back to the terminal. This wasn't the case on
4.3.x ]
[1]+ Stopped ./history | his
$ jobs -l
[1]+ 4784 Stopped (tty input) ./history
4785 Exit 127 | his
$ fg
./history | his
^C
$ jobs -l
$
Bringing the process to foreground and sending SIGINT seems to clean the
process from the job list. Is this sufficient?
On Tue, Apr 21, 2015 at 3:14 AM, Chet Ramey <chet.ra...@case.edu> wrote:
> On 4/20/15 5:24 PM, Valentin Bajrami wrote:
> > Hi Chet,
> >
> > I see. But how would I avoid this? Using Fedora 21 here and my
> > command_not_found_handle() is
>
> It's hard to say without knowing what pk-command-not-found does. What
> does this do when you just run `his' from the command line and let it
> execute in the foreground?
>
> What happens when you run `fg' to try and bring that pipeline back into
> the foreground?
>
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
> ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU c...@case.edu
> http://cnswww.cns.cwru.edu/~chet/
>
--
Met vriendelijke groet,
Valentin Bajrami
