meskio / tudu Goto Github PK

It doesn't happen if you schedule task 1 for day X, task 2 for another day and then task 3 for day X again, but otherwise it seems to always happen, whether the date is past, present or future.

While I acknowledge that project is in the "low maintenance mode", this might benefit someone.

If task has a set deadline (say 12/02/2012) and scheduled date is then set to the same date, tudu segfaults with 100% probability.

dmesg record:

tudu[596066]: segfault at 41 ip 0000555f4dbf5fd7 sp 00007ffe8fa4c7d8 error 4 in tudu[555f4dbd7000+27000]

strace excerpt:

read(0, "\r", 1)                        = 1
write(1, "\33[?25l", 6)                 = 6
rt_sigaction(SIGTSTP, {sa_handler=SIG_IGN, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0459f0cd60}, {sa_handler=0x7f045a2c9ce0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0459f0cd60}, 8) = 0
poll([{fd=0, events=POLLIN}], 1, 0)     = 0 (Timeout)
poll([{fd=0, events=POLLIN}], 1, 0)     = 0 (Timeout)
rt_sigaction(SIGTSTP, {sa_handler=0x7f045a2c9ce0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f0459f0cd60}, NULL, 8) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x41} ---
+++ killed by SIGSEGV +++

After changing the schedule column width in tudurc, when I open tudu, it sort of opens and then closes again. Then when try opening it again it gives me the warning

Lock file found

either
    Another program may be editing the same file.
    If this is the case, be careful not to end up with two
    different instances of the same file when making changes.
    Quit, or continue with caution.

or
    A tudu session for this file crashed.
    "Edit anyway" will destroy the lock file.

[E]dit anyway, [Q]uit:

This happens everytime I try to open tudu with the changed schedule column width. I can still open it, ofc, but having to go through this everytime i want to access my tasks takes away a little of the functionality of tudu for me. Is there a fix to this?

####Steps to reporoduce
Change the line row = 70%(tree,vpipe,30|schedule) # Show the schedule on the right side of screen to any other value "__|schedule".

Strangely enough, the same issue doesn't recur when changing the line above this one,
row = 1(blank,vpipe,50|blank)

Right now a task is either 100% complete of 0% complete. Provide a way to enter percentage completion.

Eg. "Cycle 100 km before Jan 2021" - 30% done.

When I assign keys in .tudurc they show up properly in the ? menu and on the top bar, but they do not actually bind them to the actions. It is only visual.

To match Vi/m behavior more closely it would be nice than when we add a task Esc has the same behavior as Enter. (being a vim user I can't count the number of times I've added a task only to hit Esc at the end of the line and lose it)

Really awesome application by the way :)