1. 15

Showcasing on behalf of the author

  1.  

  2. 2

    Under features:

    A single statically-linked binary

    However:

    $> file dstask-linux-amd64 
    dstask-linux-amd64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=cu1hrEbGC51WSnrXRWmO/LxEhGHqAdR1zwX7KXo8c/ju45ya_zDU7vTVIcVwh7/e--5EJEmFx-qWIAQdnH_, stripped
    

    So, no, not a statically-linked binary, and there are several reasons why that may be

    1. 2
    2. 1

      Also see TaskWarrior, which I have been using for several years now.

      1. 1

        This is explicitly referenced in the README. Looks like this is intended to be better than TaskWarrior.

        1. 1

          Huh, I have not used their sync service. I use git to manage the files in the data directory.

          1. 3

            I started with taskwartrior, indeed using git to sync the data directory at one point. I gave up doing that after the merge conflicts (caused by the data format, and syncing across computers) were too frequent and difficult.

            I did like taskwarrior, and it’s what inspired me to write dstask after a found several things I wanted to do differently.

            1. 2

              Thanks for the history!

      2. 1

        And how do you set reminders :)

        1. 3

          That’s a planned feature, and why dstask hasn’t reached v1.0 yet. Coming soon!

          A main challenge with reminders is synchronisation. It’s important to avoid duplicate tasks when synchronising across machines – which I’d found is an issue with taskwarrior sometimes. I have a mechanism in mind to avoid this problem.