![](https://secure.gravatar.com/avatar/67d9f9f4ba171c7673178ba08015b98c.jpg?s=120&d=mm&r=g)
And using safe mode here is just to make sure that the problem is not
caused by extensions.
The annoyance started long before I bothered opening firefox with an extra
argument.
On Thu, 29 Oct 2020 at 12:02, Taco Hoekwater
On 29 Oct 2020, at 11:29, Sylvain Hubert
wrote: Hi,
sorry if this is not the best place to file a bug but I found no working bug tracker for context.
Should you not be looking for a bug tracker for firefox instead?
It looks like firefox in safe mode is perhaps trying to do something with (or waiting for ?) a shell command called ‘context’, which is presumably not related to ‘our’ ConTeXt.
You can test that by (temporarily) redirecting the ‘context’ command from ‘luametatex’ to ‘ls’ (but keep it at the same path), and see if the problem persists. If so, then it is the actual name giving problems, and then can you should file a firefox bug report because then it has nothing to do with ConText itself.
But even if the above is not the actual issue, it still sounds like a firefox problem to me.
Best wishes, Taco
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : http://contextgarden.net
___________________________________________________________________________________