Stacks

Thanks for clarifying - I am using "Run Script" with /bin/zsh & input as argv, and the zshenv file includes the import path of the rust executables ("$HOME/.cargo/env") so that would explain why it doesn't work after migrating (and why adding "export PATH=$PATH:~/.cargo/bin/" allows it to work again) I'll see if I can migrate to an external script and test.

Can you point me towards what specific release notes you are mentioning? I didn't see anything specific that mentions a need to import/source.

Thank you for sharing that link - I searched all across the Alfred docs and hadn't see it. Also thanks for mentioning $HOME - I didn't see that in the list of Alfred vars when I exported an initial list, so wasn't sure if one existed. Adding an "export PATH=" to the top of the script resolved the issue, and appears to handle the ~ correctly.

Hi Team! I have a workflow I've made that passes alfred arguments to a CLI application and executes it using the "External Script" option for ZSH, as argv, like so: command -q ${query} This no longer works on the latest pre-release (5.1.2) and quit working (no changes), so I have reached out to support. I found that it does work if I replace with the full path, i.e. /users/user.name/.bin/command -q ${query} However, that path will be different depending on the user, so it's not ideal. However, using "~/.bin/command -q" does not work and returns a "Command not found" What is the best way of handling this? All of the above work successfully from the CLI directly.

Right/cntrl-click on the workflow, then select "Configure...." And make sure "Task Prefix" is blank I don't see any GitHub issue - where did you open?

I'm not sure how you could be getting 'tdbuy apples', as the "td" should be the alfred action. Open a github issue with your debug log and we can take a look. Did you configure "td" as your task_prefix by chance? (you probably want that blank) Todoist NLP is done by Todoist, not me. I have no control over it. According to Todoist, they support several languages, but you would have to reach out to their support to confirm. I believe it works based on what your language setting in your Todoist account is set to.

You're welcome!

Thanks, updated. Two questions: 1) Is there a better way to compile the alfred workflow without manually uploading the release each time? (I saw some Github actions, but wasn't sure how to use them) 2) For my workflow, I need to take the input from the keyword and I want to be able to post a notification with that text (while also passing it to the script input and parsing the output). So, I set the input as a variable, and then used the $1 you mentioned above throughout the script to pass in the input/output of each stage, while then calling input at the end. Is there a better or built-in way of doing that?

Appreciate the Feedback - thank you! I will work to get those updated. On the github repo notes - do you have a guide for how to upload the files? I saw that on other repos, but didn't see a way to export the files from Alfred (only the final .alfredworkflow bundle)

My primary workflow within Todoist and Alfred is to quickly capture any ideas on my mind and put them into my Todoist inbox for later GTD processing, categorization, and labeling during my daily/weekly review sessions. (I use my Todoist Inbox as my single GTD Inbox across all platforms and clients - from Email, phone, camera, etc) I previously used the https://github.com/moranje/alfred-workflow-todoist workflow, but the structured format was offputting, and it began to truncate many of my tasks after the last update (so I would get tasks in my Inbox that only contained half of what I had entered). Since my primary workflow requires fast input of a single entered string, I went looking for a new solution, and I found a great CLI app that adds tasks extremely efficiently here (https://github.com/alanvardy/tod) So, I wrote an Alfred wrapper for it that adds the tasks to the Inbox and makes my workflow much more efficient. I wanted to share in hopes that it is helpful - I'm fairly new at this, so I would love any feedback on the way I did it Workflow can be found here https://github.com/stacksjb/AlfredTodWorkflow (or on Packal once approved)

Hi Vero, I worked with Alfred support and identified the issue. I don't heavily use this workflow anymore so I didn't troubleshoot it further. It's related to an issue with Python which causes Python to crash when this workflow is executed or the calendar app is launched, and only happens on Big Sur (did not happen on previous OS).

FYI, this workflow crashes and does not function on Big Sur

Hi Martien, I've run into an issue where every task I submit returns a 400 error, but if I mark a task as complete and then re-try, it works. Some sort of issue with caching? I've posted on the Github issues as well. EDIT: Identified the issue. You cannot submit more than 300 tasks. The reason completing, then creating works is because it takes you to 299. Todoist has a hard limit of 300.