-
-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guidance requested: Recurring task import behavior #3458
Comments
I don't think If you'd like to use The other option is to actually interface with the data directly, using taskchampion, rather than through the |
Thank you very much! I will discuss with @jspricke how to move forward so I can produce a patch. If you don't mind we can leave this open in case any detailed questions come up. The Rust API sounds interesting- would it be more or less straight forward for a contributor to expose as a C library? |
Yes, interfacing with Rust from C is possible, but requires "glue" for types like strings, and adhering to Rust's safety requirements. https://github.com/GothenburgBitFactory/taskwarrior/tree/develop/src/tc/lib/src is an attempt to do such a thing. |
Note also the Python bindings being built in GothenburgBitFactory/taskchampion#385 |
I am working to improve a library to convert caldav task data and store it in taskwarrior in jspricke/python-icstask#6 . (icstask powers radicale_remind which provides two-way publishing taskwarrior tasks and remind events for use on phones/office software... it's amazing)
I ran into an issue using
import
to update an existing recurring task.Is there a way to use the import command to update a recurring task while letting taskwarrior know it is just to update the information and possibly propagate according to configuration, not change recurrence status?
Thanks!!
The text was updated successfully, but these errors were encountered: