On Sat, Nov 16, 2013 at 6:53 PM, j. van den hoff <[email protected]>wrote:
> coming back to the "limit reached" messages recently added to the > `timeline' output: > 1. > the fact that `fossil timeline' by default does not (as most other RCSs) > display the full timeline but rather a very small fraction > should be known to everybody using `fossil' (there are really > substantially less easy to find bits of information in the help pages...) > so I find the 'line limit (20) reached' message completely redundant. I > _know_ that... > New users of Fossil might not read enough of the documentation to actually know this. Also, this helps when scripting Fossil commands by providing an unambiguous "end of data" indication. (Simply running out of data could be an error. Explicitly indicating the end of data avoids this ambiguity.) > 2. > now, if I type `fossil timeline -n 20' the system tells me (most of the > time, about from day 1 or 2 of the project...): > "entry limit (20) reached". yes, I know _that_ one, too, since I've just > typed it. > See previous. Agreed this is inconsistent with #1. > > 3. > if I type `fossil timeline -n 0' instead I get "end of timeline (nnn)". > guess what? I know it (except the nnn value which I don't need) already... > Again, previous applies. > > 4. > a related thing: `-n N' restricts the display to N entries while the > "default" of this option is to display 20 lines. this is not really > consistent in my view. it would seem better to specify the default as a > certain number of entries, too (and thus drop the distinction between > messages no. 1 and 2 above) Yes, I agree these should be made consistent.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
