'fossil timeline -n 0 after current' doesn't return timeline
(1) By John Rouillard (rouilj) on 2025-05-08 01:11:29 [source]
Hi all:
At some point the -n
option when used with timeline after current
changed. For example:
% fossil timeline -n 0 after current
+++ end of timeline (0) +++
It used to work to provide a list of all timeline entries (wiki and
check-ins) after the date of the current checkout in my working directory.
If I change it to:
% fossil timeline -n 1000 after current
=== 2025-05-07 ===
13:23:14 [ea40cbb0c0] Adjust comment to http_build_login_card() to include
clarification regarding the source of randomness in NONCE for the
login card. No functional changes. (user: andybradford tags: trunk)
=== 2025-05-06 ===
[...]
=== 2025-04-30 ===
17:21:50 [a8457a53fb] Edit to wiki page "Release Build How-To" (user: drh)
16:57:32 [1205ec86cb] *CURRENT* Version 2.26 (user: drh tags: trunk, release,
version-2.26)
It works as expected.
If I use: before
, descendants
/children
, ancestors
/parents
in
place of after
it works as expected going all the way to the first
check-in in 2007 or the latest check-in.
Version: This is fossil version 2.26 [2116238e80] 2025-04-20 16:54:38 UTC
with the checkout/working directory at 1205ec86cb
.
(2) By Martin Gagnon (mgagnon) on 2025-05-08 11:37:47 in reply to 1 [link] [source]
At some point the -n option when used with timeline after current changed ...
It should be fixed on trunk.
It's my fault... I recently fixed the use of the "after" keyword which was not working properly for many cases, but I've overlooked the special case with "-n 0".
Before, all cases like:
fossil timeline -n N after B
- where N is smaller than the number of checkins between latest checkin and B.
was not working as expected. - example:
fossil timeline -n 2 after 1980-01-01
was showing the 2 checkins after the 2 most recent ones overall.
- where N is smaller than the number of checkins between latest checkin and B.
References:
Related branch: fix-timeline-cli-after
Related forum post