On Thu, May 29, 2014 at 6:22 PM, Michai Ramakers <m.ramak...@gmail.com> wrote:
> Right - that's clear, thanks. This is not a big issue and indeed > eventually always gets solved. Just something new users may encounter. > i agree, i just don't see a way to do this consistently (for all commands) in the current code base because the bits which trigger such errors will normally cause fossil to exit before the command-level code could tell the user "hey, this might be due to a permissions problem." -- ----- 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
