On 1/14/2016 7:40 AM, Andy Bradford wrote:
For now, instead of relying on environment variables which have lower precedence, I've made the test just use a local editor setting in the test repository that is being used:
That seems best. Use the highest priority control rather than the absolute lowest priority control. That will keep the test suite protected from people who had an actual good reason for a global setting.
I wonder if there are other test cases that are susceptible to "interesting" settings either in the environment or global settings?
I suppose that is another attack surface to add to my list of places to consider fuzz testing.
-- Ross Berteig r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
