concept for calculation of a task's id about ttodo_vim HOT 4 CLOSED

from ttodo_vim.

from ttodo_vim.

Hi @tomtom . Thanks for clarification. I use the todotxt format in an environment, where there are multiple people working simultaneously on different and even the same todo files, shared via a common file-based synchronization method like NextCloud. Potentially 1000 people working in collaboration within a shared project. This environment makes it rather possible to accidentally hit the same microsecond when creating a new task on one of the multiple task files. So, I personally like the former concept better, where you created an id in dependence of the task's textual content rather than a timestamp alone.

And the ID should be as short as possible and consist only of
alhpanumeric characters.

That is a good requirement for short, human-readable text lines. And it is rather pleasing to the eye ;-) .

The ID should be unique at the time of creation. Once a task got an ID
assigned to, the ID is not supposed to be changed.

That should be common practice for any task management system. Even if tasks are completed and transferred to the done file, their ID shouldn't be reusable within the same project.

The ID is not meant to be unique across machines, users, todo files etc.

In my environment, the ID sould rather be exactly that. unique as far as possible.

How come, you changed the concept for id calculation for vim >= 8? Were you forced by some technical issues? Or does the new id calculation concept promise a smaller probability for collisions? Would it be possible to maybe offer both concepts (selectable via a configuration parameter)? Or maybe combine them for even lesser collision probability?

from ttodo_vim.

from ttodo_vim.