tasks requiring confirmation

[migueldvb]

When I run a task that requires confirmation from vim-taskwarrior such as deleting an order the command fails.

:!task 107 delete                                                                                     

Delete task 107 'update order'? (yes/no) Task not deleted.
Deleted 0 tasks.
shell returned 1

I'm using neovim 0.2.2. Is there any way to confirm the task deletion from vim-taskwarrior?

[DarrienG]

Same issue here.

[arooni]

ditto / tritto (three people with the same issue?) lol

[Aerex]

This is a really old issue but has this been resolved? I am dealing with the same problem. Is it possible to simply use something like Dispatch so that it doesn't use the default ?

[arooni]

also fails with task undo.

[xarthurx]

taskwarrior 2.4.0 starts to allow rc.confirmation=no for a non-interactive shell command.

Since this repo is not maintained any more, I've fixed it in my fork (hopefully will keep adding new things), and available here:

https://github.com/xarthurx/vim-taskwarrior

[DarrienG]

The hero we need but don't deserve 😭

[xarthurx]

The undo should also be fixed now. @arooni

The main problem is that vim doesn't encourage interactive-type of command.
So what I do in the fork is to fake a confirmation with vimscript, and suppress the shell interaction with rc.confirmation=no.

I'll be first implementing meaningful fixes based on the issues in this repo for the past 2 years, then see if it make sense to add more functionalities from newer TaskWarrior.

There's also an alternative way to interactive with TaskWarrior with tasklib.
(This is my beginning attempt to work with TaskWarrior from WSL by contributing PRs, but doesn't work out well with it + taskwiki -- I end up here with this plugin)

Please feel free to try out the fork and submit issues/PRs.

[xarthurx]

for the command of deleting, please use either :TWDelete or the shortcut D instead of pure shell command :!task xx delete.

The latter is a pure shell cmd and vim cannot handle the interaction.

Though of course you can do :!task xx delete rc.confirmation=no if you like.

[PhilippWoelfel]

@xarthurx : Tried your fork, but I am getting errors. Where can I submit an issue?

[xarthurx]

@PhilippWoelfel Thank you for the test. Yeah, there're several annoying things I've noticed, and I'm constantly adding things recently, though during weekends. Please submit in my fork, so that I'll follow them and look into them.

…

On Thu, 16 May 2019 at 19:45, Philipp Woelfel ***@***.***> wrote: @xarthurx <https://github.com/xarthurx> : Tried your fork, but I am getting errors. Where can I submit an issue? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#142?email_source=notifications&email_token=AAOVGVRL2NYF5TAXZHJII6LPVWMTJA5CNFSM4EKXFFY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVSR2HA#issuecomment-493165852>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOVGVWSO5AALR7SZHO5FB3PVWMTJANCNFSM4EKXFFYQ> .

-- MA Zhao *"SAVE PAPER - PLEASE THINK BEFORE YOU PRINT!"*