Jump to content


  • Content Count

  • Joined

  • Last visited

About GoOz

  • Rank

Contact Methods

  • Twitter

Profile Information

  • Location
    Paris, France

Recent Profile Visitors

446 profile views
  1. No, it doesn't work anymore. And when it worked, it didn't output this feedback that's why I thought it was an error.
  2. Sorry I have no clue either. Last time it was "fixed" when I uninstalled and reinstalled the workflow. Didn't try it yet. But I'm pretty sure it's not related to the request or the WordReference's API itself. EDIT: I just uninstalled/reinstalled it and the path is now fixed but I still get `Script with argument '(null)' finished` 😢
  3. Hey @avk_tp It's me again I have the same issue, again. As Alfred 4 came out, I decided to clean a little bit, uninstalled Alfred and installed the new version. It turns out I still get the same error for the missing "Alfred 2" folder. I took a look in your code and found this line. I'm starting to think that this is the issue. I also get the `Script with argument '(null)' finished` but one thing at a time. What do you think?
  4. Oddly, I'm on Alfred 3 as well (3.7.1 to be exact) 😐 I tried to reinstall on top of it but It wouldn't fix the issue. I just tried to remove the workflow and reinstall it again and… now it works! ☜(゚ヮ゚☜) Don't know why I didn't think of that before. Sorry for the bother.
  5. Hey there, @avk_tp I'm one of the lucky few who had a API key before WR closed it. So until recently it worked perfectly, but today I have a weird issue. First I had an error saying it could mkdir inside… /Library/Caches/com.runningwithcrayons.Alfred-2/Workflow Data/ …that this folder didn't exist. So I made the missing folder "Workflow Data" myself and then the workflow was able to write a "wordreference" folder inside but now, it's still not working. In the debugging console I have [2018-12-18 16:10:32][input.scriptfilter] Queuing argument 'house' [2018-12-18 16:10:32][input.scriptfilter] Script with argument '(null)' finished Don't know what's going on but I tested the API and it's manually responding so it's not that. If you have any clue, it would very much appreciated.
  6. So if i understood this correctly, if i use a external script, in my case Gifify, i can't make it silent ? What i would like to do is select a movie file > run Gifify with notifications of what going on but without opening the terminal. That can't be done, right?
  7. And now it's perfect… but i found another issue. When an app has multiple windows, for example Adium (Contact list and messages), it seems that, even if i focus the message window, it resizes the contact list. :/
  8. Wow. AWESOME ! Just have one tiny feedback : I use the full black theme "Minimalist Dark" by Hannes Egler and your icons are confusing because i only can see the white part of them. For example, i can't see the "full" icon xD And that's it.
  9. I thought i'd give it a try and there is my first workflow. Nothing big here but here it is. Translate a given DOS path (file or folder) to a UNIX path and reveal it with Finder For the times when your coworkers give you DOS path to files on your network and you want to get there quickly, use this. Advice For an easier use, mounted volumes must have the same name on both PC and Mac computers on your network. Usage Type the keyword "path" then type the DOS path you want to convert. It will open Finder to file:///Volumes/C/Share/specs Features The new converted UNIX path will be pasted in your clipboard. Links Homepage Download worflow
  10. OK, got it. Don't know why but it seems that, after my sed, my {query} had a trailing newline. I added "tr -d '\n' at the end because having "echo -n '{query}'" didn't change anything, so now we're done. Finally works like i wanted
  11. Damn, you're good. Well in my example, if i add -n, it does work. But oddly, as i explained in the original topic, it wouldn't work if i translate with a sed. I had echo -n "{query}" | sed -e 's/://g;s/\\/\//g;s/^\(.*\)$/file:\/\/\/Volumes\/\1/' and the output had still the newline. The query before sed hasn't the newline and after it has it. I finally got it with a tr -d '\n' Took me a week to figure it out. Anyway, i can't find how to flag the topic as resolved, i guess you do that, right?
  12. Bug reproduced at both home and work. Configs : @home: OSX: 10.7 Alfred: v2.0.1 build 173 @work: OSX: 10.6 Alfred: v2.0.1 build 173 Origin This topic Step to reproduce NB: I did a brand new workflow to be sure it was clean of any extra hidden space or carriage return. Basically it looks like this: A keyword object with arg to pass the {query} Run Script object uses /bin/bash and simply does an echo "foobar" Output 1 displays the {query} Output 2 displays display the text in the text field (e.g. foobar) Output 3 displays the {query} passed by the script. When i trigger the workflow with "foobar" as an argument, this is what i got : As you can see the {query} passed by the script has an extra space at the bottom. As harmless as it seems, it's not Can't properly use the {query} in a bash script because of this. Do you confirm?
  13. So… i've been investigating. Tried many things to spot the filthy glitch. I finally realised that the output has an extra carriage return, just before the closing quote i guess, which could explain why my command open with firefox doesn't work. To be sure i made a test by adding another notification output : Nb: In the first script i just put an "echo "foobar"" The first notification has a {query} in the input Text. The second has "foobar" in the input Text. And this is what i got: You can see that the first one has an extra space. Do you think it's a bug and if so, i should post it in the bug section of this forum, right ?
  14. So am i. Thanks again to you for that neat multitask workflow
  • Create New...