Thus said Jan Nijtmans on Thu, 23 Oct 2014 22:56:59 +0200:

> Because of consistance  I would prefer every Displayed UUID  to have a
> short format (%S), while every  hyperlink containing an UUID would use
> the full length. That means, I would prefer to keep this part as it is
> now by default. Sorry .... ;-(

I could  be wrong, but  is it  possible that what  he's asking for  is a
consistency  in a  fixed  output width  when  %S is  being  used in  the
timeline?  Or an  option  to have  fixed width  UUIDs  in the  timeline?
Consider  the  timeline  output  here  where you  have  a  nicely  fixed
width  column of  UUIDs and  then suddenly  to break  the flow  there is
[84871722547960b] in the  middle. I can imaging it  getting pretty messy
if there are a lot of varying widths of UUIDs in the output.

=== 2007-10-09 ===
02:35:22 [dfea940da8] Refinements to the timeline for giving better information 
about wiki pages. (user: drh tags: trunk)
=== 2007-10-07 ===
14:38:54 [a21806dcf3] Fixed omitsign discrepancies. Windows version now looks 
for USERNAME instead of USER when creating new database. (user: jnc tags: trunk)
=== 2007-10-06 ===
22:13:25 [70b0aa899a] Found easier way to access the typevariables of 
singletons when writing the rcs parser. Now moved the other singletons to the 
same construction. (user: aku tags: trunk)
22:06:05 [84871722547960b] Broke static dependency cycle repository <- project 
<- file <- repository, now using dynamic/runtime object references instead. 
This allows us to keep the nice and readable format for our files, code is 
readable too. (user: aku tags: trunk)
21:59:03 [3d88cfd05d] Started capture of revision information in file objects. 
Capturing authors and commit messages and repository level. Completed 
persistence for these latter too. Rearranged the requirements, imports, and 
exports a bit to handle the new dependency cycle repository <- project <- file 
<-
         repository (user: aku tags: trunk)
21:19:26 [6d1811d61e] Continued work on pass II, skeleton of it completed by 
adding outline of code for persistence. (user: aku tags: trunk)
21:01:15 [2e3815c3b4] Added skeleton and dump methods to make file objects 
proper sinks for the rcs parser. (user: aku tags: trunk)
21:00:48 [e7bb3d073d] rcs parser rewritten to snit type, singleton, using 
callbacks to convey information. Got a grip on regexp -start -indices (^ -> \A, 
indices are absolute). This means that I now don't have to shift the 
unprocessed string down in memory, it is all index processing now. This makes 
for a much
         faster parser, especially for large files with many revisions 
(example: ChangeLogs). (user: aku tags: trunk)
20:58:24 [ec053168a8] Nicer parser integration into pass II, and sort files for 
easier filesystem traversal during parsing. (user: aku tags: trunk)
18:43:01 [8a93ffa9c1] Fleshed out pass II, added skeleton of rcs archive class, 
started integration of rcs parser. (user: aku tags: trunk)
18:28:33 [860f533e98] Bringing back in the old parser for rcs archives. (user: 
aku tags: trunk)
17:10:47 [488afb9746] Enforce well-formedness constraints on wiki pagenames. 
(user: drh tags: trunk)
16:40:48 [3cdb768fca] Do not attempt to access the global_config table if the 
~/.fossil database has not been opened. (user: drh tags: trunk)
16:37:39 [6d58613757] Timeline comments are now rendered as wiki. Wiki changes 
appear on the timeline. (user: drh tags: trunk)
13:13:33 [bf428e6854] Now able to enter and edit and display wiki pages. Still 
many problems to be resolved. (user: drh tags: trunk)
--- line limit (20) reached ---

Andy
--
TAI64 timestamp: 40000000544971b5
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to