Kevin, great catch! I can't believe no one spotted this before. I've fixed the mistake now. I'm actually planning to rewrite the entire workflow when I get a chance. I've learned a lot about making Alfred workflows since back when I did this one, so I think I can do a much better job now. Thanks for letting me know about this - glad you got it working.
Hey Robert, thanks for your Alfred workflow for Clop. It's fantastic. The only issue I have is that I can't work out how to save the optimised file with a new name, i.e. without overwriting the original. Is there something inside the workflow that I can modify to achieve this? I have a template name set up in Clop itself, but that doesn't seem to be applied when I use the workflow. Thanks again, David
Hey David. If it's something that can be done via the CLI then you can do it with the workflow. However, you'll need to modify the actual script that is being run at the end (where the Clop command is being run). Unfortunately I'm traveling and away from my Mac for about a week, so I can't send screenshots or dive into this right now, but if you can't find the script block to modify then let me know. The way to create name templates via the CLI may also be different but I think you can see how it all works by running `Clop -h` on terminal.
Thanks so much for your quick reply. I'm about to step away from my own computer for a couple of weeks so there's no rush on this. (There's no rush anyway – a nice to have.) I had a quick look at the script block but it is way beyond my skill set to be digging into it without guidance. If and when you have a moment when you're back, I'd appreciate some instruction.
2. Take a look at how to build your templates for use via the CLI. You can run `clop optimise -h` in terminal. Or here's a screenshot of the important part: https://i.imgur.com/4JgENXd.png
3. Here's the part of the code that you need to modify in the Alfred workflow script block. I'm using the exact same example that the CLI help shows: https://i.imgur.com/8l07BWM.jpeg (make sure to escape the path with \" \")
Hi Robert, finally got the chance to play with this ... and it works a treat! Thanks so much for the detailed step through – and for your Clop workflow in the first place. This will speed up my own work enormously. 🙏
Hi, super helpful thanks. But I am having issues with the Alfred Workflow, have you found any issues recently? I added the shortcuts into the workflow, but the only one that does anything is CTRL + SHIFT + O which opens Alfred with he options. However, Clop doesn't execute anything. Also, typing Clop as a universal action, doesn't show anything? What did I miss =-/
Did you install Clop's CLI? https://i.imgur.com/BWr9i01.jpeg <- That's required for everything to work. If you got Clop CLI's installed, and if you can run Clop's commands in Terminal then the workflow should also have no issues. You can check on Terminal by simply typing clop. It should show you an OVERVIEW text that tells you it is installed. I'm using it without problems but if you already got the CLI I can help you debug. Probably checking the debug window in Alfred will be useful.
You can use the real path of Clop CLI:
/Applications/Clop.app/Contents/SharedSupport/ClopCLI
Which will don't need to click on Install command-line integrations and make sure everyone will get the right one.
BTW, Thank you very much for sharing me this software and workflow.
oh nice, thank you so much for sharing! I'm planning an update to this workflow sometime in the future and will definitely keep this in mind.
Hi, thanks for that. Was still having issues after I installed Clop's CLI and I think I found the error:
[10:53:49.407] ERROR: Clop[Run Script] (eval):1: no such file or directory: /Users/ognistik/.local/bin/clop
the user path was wrong. It worked after I went in and edited it.
Kevin, great catch! I can't believe no one spotted this before. I've fixed the mistake now. I'm actually planning to rewrite the entire workflow when I get a chance. I've learned a lot about making Alfred workflows since back when I did this one, so I think I can do a much better job now. Thanks for letting me know about this - glad you got it working.
Thank you for this great info and I have subscribed
Very generous share as usual. Much appreciated.
Hey Robert, thanks for your Alfred workflow for Clop. It's fantastic. The only issue I have is that I can't work out how to save the optimised file with a new name, i.e. without overwriting the original. Is there something inside the workflow that I can modify to achieve this? I have a template name set up in Clop itself, but that doesn't seem to be applied when I use the workflow. Thanks again, David
Hey David. If it's something that can be done via the CLI then you can do it with the workflow. However, you'll need to modify the actual script that is being run at the end (where the Clop command is being run). Unfortunately I'm traveling and away from my Mac for about a week, so I can't send screenshots or dive into this right now, but if you can't find the script block to modify then let me know. The way to create name templates via the CLI may also be different but I think you can see how it all works by running `Clop -h` on terminal.
Thanks so much for your quick reply. I'm about to step away from my own computer for a couple of weeks so there's no rush on this. (There's no rush anyway – a nice to have.) I had a quick look at the script block but it is way beyond my skill set to be digging into it without guidance. If and when you have a moment when you're back, I'd appreciate some instruction.
Hi David. I'm back to my computer, so just letting you know what you need to do to change the location/name of your optimized files.
1. First, locate the script block in the Alfred workflow: https://i.imgur.com/0E7wqGy.jpeg
2. Take a look at how to build your templates for use via the CLI. You can run `clop optimise -h` in terminal. Or here's a screenshot of the important part: https://i.imgur.com/4JgENXd.png
3. Here's the part of the code that you need to modify in the Alfred workflow script block. I'm using the exact same example that the CLI help shows: https://i.imgur.com/8l07BWM.jpeg (make sure to escape the path with \" \")
Hope this helps!
Hi Robert, finally got the chance to play with this ... and it works a treat! Thanks so much for the detailed step through – and for your Clop workflow in the first place. This will speed up my own work enormously. 🙏
Hi, super helpful thanks. But I am having issues with the Alfred Workflow, have you found any issues recently? I added the shortcuts into the workflow, but the only one that does anything is CTRL + SHIFT + O which opens Alfred with he options. However, Clop doesn't execute anything. Also, typing Clop as a universal action, doesn't show anything? What did I miss =-/
Did you install Clop's CLI? https://i.imgur.com/BWr9i01.jpeg <- That's required for everything to work. If you got Clop CLI's installed, and if you can run Clop's commands in Terminal then the workflow should also have no issues. You can check on Terminal by simply typing clop. It should show you an OVERVIEW text that tells you it is installed. I'm using it without problems but if you already got the CLI I can help you debug. Probably checking the debug window in Alfred will be useful.