Implement tagging/annotation

[ErikBjare]

@TY2U first wrote about it here: #93

There's a nice video from ManicTime here showing it off: https://youtu.be/OlfknjggACQ

I wrote a little about how it would work in ActivityWatch-terms here: #93 (comment)

There is another person that seems to be interested in developing a ManicTime replacement from a gist he has written here.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[ErikBjare]

In #106 something similar was requested, there I presented a possible solution:

One thing I have in mind is to add some kind of automated tagging system based on pattern matching. It would basically work as follows: All AFK-filtered titles/URLs would be run through a pattern (such as your project name) and we'd then get out all the events relating to your project, which could in turn be used to calculate the time spent on that project.

...or at least a lower bound. A lot of activity surrounding such work might be looking up resources that can't reliably be known as related. This sounds like a future project for aw-analysis. An approximation of the total time would be the matched time + the time of temporally nearby work-related activities (GitHub/StackOverflow/Wikipedia/Slack/etc.).

[yratof]

As an additional thought on this – manually tagging / flagging would also be quite a nice option. Writing rules for catching tags, ie: if url contains website.io then tag with Project A; If terminal chooses directory and git remote -v is repo url, tag Project B. Being able to quantify user defined projects would help in my line of work greatly

[johan-bjareholt]

@yratof Running git remove -v every time you change would need an console watcher though. Has more usecases than just checking git though so that could possibly be a nice addition.

It could be made simply with aw-watcher-window though if you for example used vim, you could use set title in your .vimrc so it changes the windowtitle of your terminal to something like "yourfilename (path to your file) - vim". Then after that once automatic tagging after titles are implemented you can just grep the projectname in the titles. You can do a similar thing with bash/zsh/fish which changes the title of the window to include the current path, so it would also work even if you for example are compiling, using grep/less/whatever to find and read code etc.

[ErikBjare]

+1 on simply using window titles/URLs to autotag.

arbtt takes this approach to everything it does (ensure applications set informative titles) and while it takes some work for the user in some cases it's usually a lot easier and performance friendly than running commands in the background of the terminal to get info.