On Mon, Nov 19, 2012 at 4:30 PM, j. v. d. hoff <[email protected]>wrote:
> hi there, > > a modest suggestion: > > I would prefer (and I believe it actually would be more correct, thought > what's "correct" is always arguable) > if `fossil set' would explicitly report not only explicitly set (local) > and (global) parameters but also the > default values (whose values I tend to only partly memorize...). so > filling in all the "empty" fields a la > > autosync (default) on > > would be better, I believe. any opinions on that? > I don't know about the user interface, but I've been thinking for a long time that the internal C APIs for settings need to be fixed to make use of a single global table of default values, rather than depending each setting query to specify the default value. > > regards, > joerg > > -- > Using Opera's revolutionary email client: http://www.opera.com/mail/ > ______________________________**_________________ > fossil-users mailing list > [email protected].**org <[email protected]> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
