Jump to content

vitor

Staff
  • Posts

    8,497
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by vitor

  1. When asking about an existing Workflow, it’s best to use its own forum thread. While it may seem that starting a new thread could give your problem visibility, it fragments the discussion and makes it less likely the author and users of the workflow (the people who can help) will see it. I’ve moved your post to the correct thread. As to the problem in question, if you try it on the website you’ll get the same message. In other words, it seems like they’re experiencing an issue. Please try again later and contact them if the issue persists.
  2. Thank you for the chuckle! I’ll go straight to the links. I recommend you check the Getting Started Guide for an interactive tutorial on making a workflow. Then perhaps check some of the “Good for Learning” workflows in the Gallery. Then try something out and check the forum once you need specific help (please be sure to always share a link to your workflow and be as explicit as possible in your goal). Hope that helps.
  3. As you noted that would not work on other machines, so it is not the described solution. You either set it in your script on or the Run Script where you’re calling the Python script from, with export PYTHONPATH='path_here', replacing path_here with the relative path. You don’t touch the Workflow Environment Variables section at all. This is why it is recommended to always share a barebones version of your workflow when asking for help. I can’t really guide you more specifically because I can’t see what specifically you have done.
  4. To include a Python package with the workflow, use the --target option to set it somewhere inside the workflow’s folder and set PYTHONPATH to that path. For portability make it a relative path, not an absolute one (workflows start running from their own directory). StackOverflow has other options and examples. Make sure to install with /usr/bin/python3 so packages are built with the system python. See also Understanding the Scripting Environment.
  5. Updated to 2024.1. New repository.New icons.New About.Add configurable keyword.Add configurable player keys.Updated code.Remove OneUpdater in favour of Gallery updating.
  6. They are, but you have to access them as the language expects. In this case as ${tag} and ${path} (see link posted by @Stephen_C). But don’t use path at all to avoid conflicts. By splitting arguments (refer to @Stephen_C’s other link) you can either have them as variables or as separate arguments, for ${1} and so forth. I still encourage you to finish the workflow for the learning experience, but what you want can be accomplished in Alfred without any code: See Label Colour Tag, which will also help with your specific questions.
  7. The setting that governs that is Alfred Preferences → Features → Clipboard History → Advanced → Ignore data marked as Concealed.
  8. Thank you for the kind words. Due to the nature of the operation, the alternative would be to check all possible actions on every banner then perform on the one whose name indicates it closes the notification. However, that is considerably slower and it would require getting the names of the Close and Clear All operations in every language, which either requires configuration or becoming even slower. I spent a ton of time on that. In other words, there’s always a trade-off. I picked the least annoying one. Maybe you can change Slack’s notification type to be different?
  9. Try replacing the Open File with a Run Script Action. Leave everything at the default but make the Script: open -a 'Secure File Deletion' "${@}" Does that work for you? If not, what does the debugger say?
  10. Welcome @jrk, You can make a workflow to connect a Keyword Input to an Open URL Action, which lets you define the browser. See the Getting Started Guide for an interactive tutorial on making a workflow.
  11. That’s due to changes Apple has been making for a few OSs which are making preferences harder to use from the outside. That’s why you get that generic icon too. On the Alfred Gallery there is System Settings and Open macOS Settings Panes. Both solve the issue in different ways. They are in English, but you can edit them to the Spanish names.
  12. Alfred uses standard macOS APIs. If your underlying operating system is misbehaving, that’s what you need to fix. Check a more general forum for macOS (such as MacRumors, or Apple’s own Forums), where you’re more likely to find someone with the same problem.
  13. It can’t return back to search because it doesn’t know you got there through search. You could’ve selected files in the Finder, or used a custom File Filter, or Script Filter, or gone through the navigation pane, or any other combination. This workflow is meant to be flexible and work from any place. What you’re asking for is specific to your usage so you’d need to make a workflow which behaves that way.
  14. Thank you for the kind words. You can only rename one file at a time. Renaming multiple is a complex action usually involving some kind of sequencing, and renaming multiple to entirely different things even more so. I’ve never seen a way to do it that I found ideal, neither in GUIs nor in CLIs (and I wrote some, too). The ones that get close still require understanding the rules beforehand. It would also be incompatible with the feature to reopen the Universal Actions panel after renaming, which I find immensely more valuable and have a need for significantly more often. I don’t intend to add the feature unless the solution is so good and clear to regular users that it’s worth a rewrite of the workflow (which likely would need to happen).
  15. Updated to 2024.1. ↩ now deletes the path and reruns the search.⌘↩ removes path from list for current run and reruns.⇧↩ adds path to File Buffer.Updated icon.
  16. As you can see, those are different. And it seems like the one in Google Drive has tighter permissions. Change everyone to Solo lectura.
  17. That link says the video is no longer available. Either way, everything is correctly set up. Try any link by running yt-dlp in the Terminal, that’s what the workflow uses. If you get an error, report that one to them as they’re the ones with the power to fix it.
  18. Your Run Script has a mistake: "${$1}" should be "${1}".
  19. They would have to be executable on any macOS, that’s a Unix thing. Yep, that’s the correct solution. Removing and reinstalling the workflow should get you to that state too, since the most likely reason for that file to not executable is that it lost its permission.
  20. @bdruth That looks like a file permissions issue. Do you perhaps sync your preferences with Maestral? Try deleting the workflow and installing it again. That should get you sorted.
  21. Change the script to "${1}" in place of the source file and either use a Hotkey with Argument Selection in macOS or if you’re using something else use the Automation Task in Files and Folder → Selection in Finder.
  22. Welcome @Flavinsh, Update to 2024.1, just released, which fixes that.
  23. It didn’t, because you already have folders ticked in Extras. In general, it is recommended to not add too much there to not pollute results and instead use the specialised methods (or a workflow) to find files and folders.
×
×
  • Create New...