>
> i can confirm the behavior.
>
Thanks!
>
> i believe the message is in error though. because the job in the
> background is not actually stopped. there should be a different message
> instead or fish should just exit.
>
I think fish should just exit, same as bash.
I'll open an issue for it and fix it (if I can)?
>
> apart from that, the behavior is the same as bash. stopped jobs get a
> notice, and the second time bash exits and the stopped jobs are killed.
> jobs running in the background are reparented without a warning.
>
I tried the above scenario in bash. And ,to be honest, it was the first
time I saw "There are stopped jobs" msg in bash!
After the second exit, the stopped program was killed.
Regards,
-mandeep
>
> greetings, martin.
> --
> eKita - the online platform for your entire academic
> life
> hackerspace beijing -
> http://qike.info
> --
> chief engineer
> eKita.co
> pike programmer pike.lysator.liu.se
> caudium.net
> foresight developer realss.com
> foresightlinux.org
> unix sysadmin trainer developer
> societyserver.org
> Martin Bähr working in china
> http://societyserver.org/mbaehr/
>
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
