On 09/04/14 07:29, David Fifield wrote: > It gets the job done, but it sucks because the first thing you see is > the dialog and you have to know not to close it. Is there a way to > accomplish the same thing (keep the browser running, but don't show a > browser window) without raising a conspicuous dialog? > You could play further with this: $ nc -l -p 9999 & $ iceweasel -no-remote -p testing -chrome http://localhost:9999 If there's no server listening, firefox opens up a "can't connect" page. Otherwise, it continues running, with no UI, past the 3-minute TCP timeout mark, even if you kill nc in the meantime. However, I am not sure if the process is actually responsive, or simply hanging waiting for an HTTP response - so you'll need to test that. Also, there's no guarantee that firefox will keep this behaviour. Failing everything, maybe you could return a real XUL response that displays "don't close me"? X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-dev mailing list tor-dev@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev