#timewarrior — Public Fediverse posts

@alextheuxguy

#Timewarrior has a lot of fans around here, if you're comfortable with the terminal.

#Taskwarrior users: how do you use the `start` and `stop` workflow? I want to keep track of tasks that are "in-progress", but it seems that it requires one to `start` a task and then leave it running until it's `done`---stopping a task removes the start date and `task active` no longer shows the task.

An alternative is to use a special tag, like `+wip` that is separate from the `start`/`stop` workflow.

I use #Timewarrior to track the time spent on different tasks.

#FOSS #Productivity

Mein #atuin wrapped von 2024. Witziges Feature, wo doch alle immer Ihre Spotify Jahresrückblicke posten, mal eine Abwechselung.
#timewarrior #nvim #tui #cli

This felt like a modern #DoctorWho series opener. Introducing a new companion was going to be difficult after Jo. They could easily have had UNIT hire him a replacement but they go with something completely different and it works so much better #TimeWarrior

I remember not being a fan of Rubeish when I last watched this story but he is actually much more entertaining than I remembered him. Not sure if the name was meant to be antiphrasis but he is particularly useful in this story #DoctorWho #TimeWarrior

"What subservient poppycock. You're still living in the Middle Ages." I love that line (there are actually a few good comic moments in this story). Elizabeth Sladen really owns this role and delivers the dialogue perfectly #DoctorWho #TimeWarrior

I'm not sure about the probic vent. On one hand when Linx explains "it means we must always face our enemies" that sounds logical, but I'm not sure that I really get the whole honourable vibe from Sontarans that I get from Ice Warriors and Draconians #DoctorWho #TimeWarrior

While I loved the cover image for episode 1, there is something a little disturbing about this one... #DoctorWho #TimeWarrior

"You're serious, aren't you?" "About what I do, yes. Not necessarily the way I do it" This feels like a much more relaxed Jon Pertwee to me. He seems to be really having fun with this one #DoctorWho #TimeWarrior

The smoke bombs are an effective way to allow the Doctor to attack Irongron without actually using weapons, but there is definitely something reminding me of the TV Comics about much of this story #DoctorWho #TimeWarrior

I can't believe that it takes nearly 50 years for us to finally get to see a Sontaran on horse back #DoctorWho #TimeWarrior

"That's a generous admission. Especially coming from one of the fair sex" I'm going to take this as the Doctor just deliberately trying to wind Sarah up... #DoctorWho #TimeWarrior

"Is this Doctor a long shank rascal with a mighty nose?" "Nasty, brutish and short just about sums him up" "that narrow-hipped vixen" what is with all of the personal insults based on these characters appearances all of a sudden #DoctorWho #TimeWarrior

Interestingly the fact that the Sontarans have time travel technology doesn't play a bigger role in the show. When the technology is developped by the Daleks it becomes a focus of their stories. I feel like time travelling Sontarans is somewhat overlooked #DoctorWho #TimeWarrior

"Ah, yes. A race of great technical achievement, but lacking the morale to withstand a determined assault"
It's interesting that the Sontarans have detailed knowledge of the Time Lords. Their God like status continues to be watered down little by little
#DoctorWho #TimeWarrior

Linx: What is your native planet?
Doctor: Gallifrey. I am a Time Lord

Well, you wait 10 years to find out where the Doctor is from and then the answer is dropped casually in the middle of a fairly standard comic romp #DoctorWho #TimeWarrior

As companion introductions go I don't think it gets much better than this. Elizabeth Sladen nails the part from the very beginning and delivers a brilliant performance in every scene #DoctorWho #TimeWarrior

I can actually sympathise with Professor Rubeish here. Without glasses or contacts I would be exactly the same #DoctorWho #TimeWarrior

"Ah, I understand. You have a primary and secondary reproductive cycle. It is an inefficient system, you should change it" At times they may have overplayed the comedy with Strax but even in the first story there are hints of the same humour #DoctorWho #TimeWarrior

The scenes with Sarah not believing she has travelled in time make for great comedy (and yet at the same time remind me of the realistic reaction of Ian). Still they would have worked even better had she been kidnapped by Linx not hiding in the TARDIS #DoctorWho #TimeWarrior

Sometimes BBC iPlayer have some really nice cover images on these episodes #DoctorWho #TimeWarrior

This is a solid Sontaran design. I like the prosthetic, the fact the eyes are clearly visible and the ability to stick out his tongue is oddly off-putting. I'm not sure it works as a cliffhanger though #DoctorWho #TimeWarrior

I'm not going to pretend that Sarah is very well characterised with a full backstory from the off but after a few minutes I feel we know her better than we did say Dodo when she left. The Aunt Lavinia stuff definitely works better after watching SJA #DoctorWho #TimeWarrior

If I was watching at the time I would have been worried they wouldn't be able to find anyone to follow Jo Grant, but this new companion Sarah Jane seems like she might be alright actually... #DoctorWho #TimeWarrior

"Well, I'd rather a bright idea...All my eggs in one basket, so to speak" Not entirely convinced by this plan...also not sure if it just the lighting but Nicholas Courtney really doesn't look very well to me #DoctorWho #TimeWarrior

While I like all of the stuff with Linx, for some reason the rest of it always feels more like a medieval fair (not helped by Sarah later pointing this out) than a Hartnell or Troughton historical #DoctorWho #TimeWarrior

I like the Sontarans introduction. There are no battle fleets and invading armies, just a single soldier in a tiny space craft. Despite this Linx has a commanding presence from the first scene and I find myself oddly sympathetic towards him #DoctorWho #TimeWarrior

It feels like I've had an extended break since the end of #GreenDeath (it has been exactly one month) but it is finally time for Season 11, complete with the watcher version of Jon Pertwee floating down a weirdly shaped tunnel #DoctorWho #TimeWarrior

Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇

https://git.disroot.org/badrihippo/timewarrior-timeclock

Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇

https://git.disroot.org/badrihippo/timewarrior-timeclock

Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇

https://git.disroot.org/badrihippo/timewarrior-timeclock

Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇

https://git.disroot.org/badrihippo/timewarrior-timeclock

Couldn't find a way to export #timewarrior files to the #timeclock format for #PlainTextAccounting...so I made my own 😇

https://git.disroot.org/badrihippo/timewarrior-timeclock

1½ years later, ⏱️ #annextimelog¹ exists and I use it daily to track things I do/work. Even simultaneous things, one of the key features I was missing in most other #FOSS #plainText time trackers such as #timewarrior or :hledger: #hledger.

Yesterday, @matrss announced an #annextimelog or rather :gitannex: #gitAnnex plugin² to auto-export working hours from atl to the time management portal of @fzj. Wild! 😀

¹https://gitlab.com/nobodyinperson/annextimelog
²https://jugit.fz-juelich.de/m.risse/git-annex-remote-fzj-time-management

🚀 #annextimelog v0.13 brings stopping and continuing events similar to #timewarrior

> atl tr work # clock in
> atl stop work at 12 # clock out (time is optional)
> atl cont work 30min ago # clock in again

Todo handling has been improved as well:

> atl tr meeting 2h todo='send mail' # record todo with event
> atl mod meeting today set todo+='pay bills' # add todo after the fact
> atl mod todo set todo-=mail # remove todo containing 'mail'

https://pypi.org/project/annextimelog/

At this point, #annextimelog behaves similar to #timewarrior, but much more flexible:

- track simultaneous, overlapping events
- have arbitarily many open-ended events
- modify events individually
- take notes for points in time
- mark events with todos to follow-up later (e.g. after meetings)
- export to #hledger for further analysis
- pretty output with @willmcgugan's #pythonRich library
- dry-run and confirmation mode so you don't mess anything up
- conflict-free syncing with #gitAnnex
...

#annextimelog v0.5.0 brings several improvements here and there and #timewarrior-style time range specification, e.g.

> atl tr 15:00 - 10min ago work @home
> atl tr 6h ago until now coding @workplace

https://pypi.org/project/annextimelog/0.5.0/

Changelog: https://gitlab.com/nobodyinperson/annextimelog/-/blob/main/CHANGELOG.md?ref_type=heads

#Python #timeTracking #gitAnnex #gitAnnexAllTheThings

@Anachron @alerque @double_a_runi Oh, I use several cli programs on my #SailfishOS phone (native Linux). It's infinitely more productive than not being able to access your tooling at all 🙃 I do the occasional #hledger query (not recording though, that's the notes app as well for me...) and #timeTracking with #annextimelog (previously #timewarrior) on the phone.

Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).

Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).

Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).

Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).

Today my time invested in making #annextimelog payed off for the first time in a real-life situation: I could add new time tracking data from my phone without reception or network (so no upfront syncing). A later sync had no conflicts, even though I had added other stuff from my laptop and the repos were diverged. With #timewarrior or #timeclock this always led to very annoying merge conflicts, effectively enforcing a only-do-stuff-when-online-and-synced workflow (inacceptable).

#annextimelog is progressing nicely. It can now:

- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnex

everything stored in a #git repo with git annex metadata. 😊

https://pypi.org/project/annextimelog/

#timeTracking

#annextimelog is progressing nicely. It can now:

- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnex

everything stored in a #git repo with git annex metadata. 😊

https://pypi.org/project/annextimelog/

#timeTracking

#annextimelog is progressing nicely. It can now:

- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnex

everything stored in a #git repo with git annex metadata. 😊

https://pypi.org/project/annextimelog/

#timeTracking

#annextimelog is progressing nicely. It can now:

- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnex

everything stored in a #git repo with git annex metadata. 😊

https://pypi.org/project/annextimelog/

#timeTracking

#annextimelog is progressing nicely. It can now:

- track (overlapping!) events with arbitrary metadata (title, location, note, tags, arbitrary other fields)
- semi-intelligent time parsing (e.g. easy 'yesterday' reference with y10:00) 🎉 finally!! This bugged me the most with #timewarrior.
- show all tracked events
- output #hledger #timeclock and #JSON
- sync with :gitannex: #gitAnnex

everything stored in a #git repo with git annex metadata. 😊

https://pypi.org/project/annextimelog/

#timeTracking

Finishing the day with the most basic feature a time tracker can possibly have: recording a period of time. ⏱️

This is #annextimelog, the :gitannex: #gitAnnex based time tracker I'm making in the hope that it'll suit me better than #timewarrior or plain #hledger #timeclock.

I love adding configurably crazy amounts of debug output (-vvvvvvvv 😉) to my programs and @textualize's rich makes this a bliss!

https://gitlab.com/nobodyinperson/annextimelog

#Python #pythonRich

Finishing the day with the most basic feature a time tracker can possibly have: recording a period of time. ⏱️

This is #annextimelog, the :gitannex: #gitAnnex based time tracker I'm making in the hope that it'll suit me better than #timewarrior or plain #hledger #timeclock.

I love adding configurably crazy amounts of debug output (-vvvvvvvv 😉) to my programs and @textualize's rich makes this a bliss!

https://gitlab.com/nobodyinperson/annextimelog

#Python #pythonRich