You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KDE provides a handy way how to differentiate between modes of usage by activities. Btw. one of the motivations for activities is different time tracking approaches. It would be nice, if arbtt logs the current activity in e.g. $activity variable.
The shell command to access the current activity is: qdbus org.kde.ActivityManager /ActivityManager/Activities CurrentActivity>
The text was updated successfully, but these errors were encountered:
That’s kinda neat! Not sure how to best integrate this into arbtt-capture – not everybody runs KDE, so it would have to be kinda smart about detecting this, and there is complexity in talking to dbus (should I be talking to dbus directly, or use a separte tool like you proposed)…
Anyways, I’m not really actively developing arbtt right now, so probably won't happen to soon. But thanks for the suggestion!
KDE provides a handy way how to differentiate between modes of usage by activities. Btw. one of the motivations for activities is different time tracking approaches. It would be nice, if arbtt logs the current activity in e.g.
$activity
variable.The shell command to access the current activity is:
qdbus org.kde.ActivityManager /ActivityManager/Activities CurrentActivity
>The text was updated successfully, but these errors were encountered: