Is it expected that start stop only work with the first record in a day ?

[axnj2]

When there are multiple record in a same day, klog start and klog stop are only working with the first record with that date.

Example :

2025-12-25
Something #1

2025-12-25
Something else #2
    19:00 - ? 

When running klog stop, it gives this error :

Error: Manipulation failed
No open time rang

[jotaen]

This is expected behavior right now – however, not in a deliberate sense, but more by accident. Even though the spec allows multiple records for a date, I believe most people use a single record per day/date. Therefore, I think there wasn’t much practical need yet to address this properly in the klog start, klog stop (et al.) commands

Out of curiosity, what’s your use-case for multiple records per date, and what behavior would you have expected?

[axnj2]

My use case is to apply the same tag to all entries in a record without having to repeat it for each new entry in a day.

Here is for example a simplified version of my .klg for yesterday

2025-12-25
#category1    
    13:30 - 17:18 main task    
    -10m coffee break
    -48m

2025-12-25
#category2
    17:30 - 18:30  
    -11m 

2025-12-25
#category3
    20:00 - 20:12
    20:55 - ?

Here I would expect klog stop to replace the ? by the current time.

I only started using klog two days ago so I'm only figuring out how to use it correctly, I understand that another way to do this would be :

2025-12-15
    13:30 - 17:18 main task #category1
    -10m coffee break #category1
    -48m #category1
    17:30 - 18:30  #category2
    -11m  #category2
    20:00 - 20:12 #category3
    20:55 - ? #category3

But this does not look as convient to me.

Alternatively something like this seems intuitive to me to achieve the same goal (inheriting the tag for indented entries) but I believe it is not part of the spec :

2025-12-15
    13:30 - 17:18 main task #category1
        -10m coffee break 
        -48m 
    17:30 - 18:30  #category2
         -11m  
    20:00 - ? #category3
        -55m

[jotaen]

Ah, I see. Yeah, this is a bit of a shortcoming of the file spec, where if you have lots of entries that all require tagging, you’d either have to repeat them or split it up into multiple records.

In any event, I believe it makes sense to change the tooling behaviour so that the klog start/klog stop/etc. commands can deal with that situation and don’t just bail out at the first record they encounter.

[axnj2]

Thank you for the great tool, it is really usefull to me !