On Thu, Oct 6, 2011 at 12:07 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> On Wed, Oct 5, 2011 at 11:20 PM, Matt Welland <estifo...@gmail.com> wrote: > >> "fossil: unable to open file "/tmp/mrwellan/testing/test/foo.txt" for >> writing" >> >> The remainder of the message confused the developer (and me for that >> matter). >> >> > chmod 0644 foo.txt > > :-? > > or rm? > Of course it is easy to fix. But why expose your users to all the distracting and irrelevant junk in the error message? If possible report the fact that the file can't be opened and stop. The end user was confused by the message and resorted to asking me to figure it out and even I was confused by the message for a few minutes. My suggestion to fossil developers is to keep the errors from fossil clean and relevant. But it is only a suggestion. -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
