Query whether there is an ongoing activity (open time range)

[lakemike]

Is there any way to get the current status? Right now I use "print" then "| tail -2 | head -1" to see what happend last.

[jotaen]

There is no such feature at the moment.

What use-case do you have in mind? Like, are you just looking for the quickest way to view the currently ongoing entry, or do you want to somehow process the ongoing entry programmatically?

[lakemike]

I call klog from iOS shortcuts ("Run script over SSH"). This is part of a simple pomodoro timer or logging of work time from either terminal, iPhone, or MacOS. Works very well. :)
So the main use case for the "status" command would be to find out what is being tracked and display it in a shortcut. I also see a small issue with the fact that start/ stop/ switch fail a bit ungracefully in case they are called in the wrong situation. Having the status would help to call either start or switch, for instance, depending on what is going on.

[jotaen]

I also see a small issue with the fact that start/ stop/ switch fail a bit ungracefully in case they are called in the wrong situation.

Yeah, that’s a fair point. I probably wouldn’t want to introduce a dedicated command for this (like klog status), but what would you think about the following idea?

There could be a filter flag such as --open on klog print. If you consider the following sample file (work.klg):

2024-02-09
  7h Work
  17:00-18:00 Gym

2024-02-11
  30m Morning run
  8:00-? Work

Issuing klog print --open work.klg would then yield:

2024-02-11
  8:00-? Work

And issuing klog print --date=2024-02-09 --open work.klg wouldn’t yield anything, because there is no open range at 2024-02-09.

So --open would be a regular filter flag on klog print, that would behave like (and be combinable with) any other filter flag.

That way, you could manually review whether something is still ongoing, and it would also allow for a programmatic check, such as:

if [[ -n "$(klog print --today --open myfile.klg)" ]]; then
  # There is an open range
else
  # There is no open range
fi

Would that meet your needs? I think that such an --open filter flag would be a reasonable addition, and it’s also not too much work to add.

[jotaen]

Alternatives to --open could be:

• --status=OPEN, --status=CLOSED
• --entry-type=DURATION, --entry-type=OPEN_RANGE, --entry-type=RANGE

These would be more verbose, but also potentially more powerful/flexible.

[lakemike]

This would work very well for me and I would be able to use this to extract the status.
(Regarding start/switch commands, I wonder if you could add a "--force" flag? Shall I open another feature request..?)

[jotaen]

I’ve tracked the filter idea here, I think that’s a cool enhancement: #286

Regarding the --force idea, I’d see the point, but I’m still undecided. We can continue discussing this here: #287

[lakemike]

Awesome! Thanks so much!