On Wed, Feb 17, 2016 at 5:57 PM, Boruch Baum <boruch_b...@gmx.com> wrote:
> That's good to know. In the big picture, setting the $BROWSER value is > the better solution for me, on the user side, because it avoids problems with other programs. On the vendor side, if fossil ui feels a need to > They're not mutually exclusive - you can set fossil's web browser independent of BROWSER. i don't see the interoperability there? > spawn a second process to open the browser, it should make sure the > first one has been killed first. From the system design side, I'm going > to now check my general fork-bomb protection settings, and take up my > findings with the distro maintainer. i don't remember this having been reported in the the 8 years i've been listening in, and the code doesn't (AFAICS) loop on the browser call, so i currently suspect a vendor-level or xdg-thing bug. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
