fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

11K
active users

#gitAnnexAllTheThings

0 posts0 participants0 posts today

🚀 v0.12 finally closes many usage gaps and is quite fun to use now:

> atl tr work @office since 10 # start work
> atl tr 12 - 14 meeting # record smth
> atl tr boom at 16:00 title="🤯" todo="find out what that was" # one point in time, todo added
> atl stop work # stop working in the afternoon
> atl ls todo # list events marked as todo (the explosion above)
> atl mod boom set todo= # remove todo again

pypi.org/project/annextimelog/

🚀 v0.10.0 marks an important milestone: it can record, delete and now also *edit* events! 🥳 This makes it useable as an actual time tracker/logbook and due to its flexible git annex-based metadata system even as a todo list!

> atl tr for 2h meeting with=matt,mary project=A # track a meeting
> atl mod today meeting set todo # add the todo tag we forgot
> atl ls todo # lists events marked as todo

pypi.org/project/annextimelog/

🚀 v0.9.0 brings a massive code refactoring helping everything under the hood, including:

- more syntax to specify time ranges (until last week, since monday, until next Fri, mo - fr, ...)
- location field can be set with @home at=mall in=Germany,Berlin ...
- auto-generated documentation for annextimelog.* git config options

Searching and recording events works quite well now! 🥳

pypi.org/project/annextimelog/

🚀 v0.8.0 comes closer to being well useable: It is now possible to search recorded events with sophisticated syntax:

> atl ls work @home this week
> atl ls last month project=myproject with note='my.*regex'

Same syntax as for tracking events with 'atl tr'.

This plays nicely with data export to other formats, e.g.

> atl ls last month -O timeclock | hledger -f timeclock:- bal -D

pypi.org/project/annextimelog/

🚀 v0.7.0 brings several convenient cli improvements:

· common options (-v --force -O etc.) now allowed after subcmd
· --dry-run mode to first check what would be done
· new time range wordings possible:

> atl tr work the last 2h @home on project=atl
> atl tr yesterday note="day's note for the last day"
> ...

pypi.org/project/annextimelog/

Changelog: gitlab.com/nobodyinperson/anne

🚀 v0.6.0 is out with some nice improvements:

- more intuitive tracking cli, e.g.
> atl tr work @home for 2h on project=A with person=pete,mary and mood=yay
- common filler words are ignored (with, and, or, etc.)
- no-emoji mode
- improvements to help page and log messages
- better test coverage
- better removal of multiple events
- and other stuff!

pypi.org/project/annextimelog/

Changelog: gitlab.com/nobodyinperson/anne

Continued thread

In , :gitannex: takes care of resolving merge conflicts so you don't have to.

I wanted to try how feasible git annex is as a storage backend for data that is not necessarily just files. And with its versatile metadata model, it is surprisingly well suited for other stuff as well.

But yeah, *all* first reactions to 's approach were more or less 'WHY tf git annex for this!?' 😂

I will however proceed to and see how far I get 🙃

Continued thread

Afterwards, will receive much-needed (bulk) editing functionality:

# change title
> atl mod ID title=newtitle
# change end time
> atl mod ID until 10min ago
# open $EDITOR to bulk-edit all party events
> atl edit tag=party

Natural time range specification and editing functionality are the two missing things to make it really useable for serious .

gitlab.com/nobodyinperson/anne

GitLabBulk editing in $EDITOR (#8) · Issues · Yann Büchau / annextimelog · GitLab(bulk)-editing functionality in one's favourite $EDITOR is needed. I thought of opening the editor with a Markdown-style format: top-level headlines representing the...
Continued thread

Next up for is a more natural way to specify time ranges, e.g.:

> atl tr 10 - 12 title="serious stuff!"
> atl tr 10 until now note=relaxing
> atl tr work @home since 1500
> atl tr coding @library for 3h until 10min ago
...

As long as the order of the words is sensible, tags, notes, locations, etc. will be allowed to appear anywhere in between, before or after.

gitlab.com/nobodyinperson/anne

GitLabParsing of more natural language for time ranges (#6) · Issues · Yann Büchau / annextimelog · GitLabThese blocks should yield the same respectively: atl tr 2h since 14:00...

🚀 v0.4.0 released with some minor changes:

· 'now' accepted as time
· '-O cli' outputs commands to recreate the log
· CI tests against Python 3.10-3.13
· publishing to from CI

pypi.org/project/annextimelog/

See full CHANGELOG here:

gitlab.com/nobodyinperson/anne

(annextimelog is an alpha-quality cli based on :gitannex: , an attempt of mine to .)

PyPIannextimelogTrack time spent on projects, backed by Git Annex

So :python: 3.10's Structural Pattern Matching is basically for (sequences of) objects, right? 🙂

peps.python.org/pep-0636/

I will use it for the first time improving 's parsing of cli-given time ranges, e.g.

atl tr 3h since 13:00
atl tr 10:00 - now
atl tr 14:00 for 4h
atl tr y10:00 until 30min ago

This will bring it closer to in usage.

gitlab.com/nobodyinperson/anne

Python Enhancement Proposals (PEPs)PEP 636 – Structural Pattern Matching: Tutorial | peps.python.orgThis PEP is a tutorial for the pattern matching introduced by PEP 634.