Jump to content

Martien Oranje

  • Content Count

  • Joined

  • Last visited

  • Days Won


Martien Oranje last won the day on January 24 2017

Martien Oranje had the most liked content!

About Martien Oranje

  • Rank

Recent Profile Visitors

729 profile views
  1. I haven't updated myself, but I would think the workflow should be backwards compatible, since I'm not seeing anything about workflow incompatibility in the release notes.
  2. Today (en) and heute (de) I understand (seemingly) doing nothing because that's the default option. But tomorrow (en) or morgen (de) should definitely do something (and those are working on my end). Just bear with me here, while I make sure I understand fully. So if I understand right creating a task with `todo test, morgen` with the locale set to german will create a task but today (rather than the expected tomorrow) right? Martien
  3. Does what it's supposed to (from what I can see at the logs and what I have tested on my machine). I think we may have ourselves a bit of miscommunication. What did you expect the app to show? Does it work with 'Tomorrow'? For allowed date formats, check out: https://github.com/moranje/alfred-workflow-todoist#usage
  4. https://github.com/moranje/alfred-workflow-todoist#debug
  5. Do you have an error log by any chance? (See my last comment)
  6. Do you have the language set to German? Check out the docs to see how that would work. If that doesn't work see if you can find an error log for me.
  7. The problem is the comma. Anything after the comma is expected to be the date so it needs to be the last thing you specify. The reason for this is that multilanguage date string parsing is hard, and Todoist has already solved this problem. But in order to have Todoist read the date I need to to send it a string that holds just the date (string). I do this by having the date string between a comma and the end of the string. This used to be better documented but I guess I took that out with the last rewrite. Hope that helps, Martien
  8. For what it worth: the workflow needs some time to parse the text and load the cache from disk needed to populate the projects and labels. You can type as fast as yo u like, but you may need to wait a fraction of a second before you hit ENTER after the last keystroke.
  9. You may be right about the case-insensitivity, I think in this case-sensitivity may be preferred. That's a piece of documentation that stems from a time when the workflow didn't recommend projects yet. Not sure I understand the second part. Can you show me the debug output?
  10. Just to make sure: did you have a project called Collateral when submitting the above query? If it's not already there it won't be created.
  11. I added more useful error messages to the latest patch release. It should give you a helpful error if node.js isn't installed as well as when the API token is missing. Download
  12. Add you api key as explained in the docs: todo:setting token {api token} Example: todo:setting token 2d2e2a334c5f36e7a7c43b46e
  13. Great, thanks for the feedback! Martien
  14. Yes I could do that, but I fear that some control characters like `,` and `:` and `;` might be problematic. I've opted for the long way. I've spun up a beta version for @Pavel A to test. My Cyrillic literacy is not very good but seems to work. If you can confirm it works I'll merge the changes to master. https://drive.google.com/file/d/1nmdTrYqpt7Ef1Dzt1k9PAA1oVPSMiwAh/view?usp=sharing
  15. Those aren't matched by the parser either!
  • Create New...