Jump to content


  • Content Count

  • Joined

  • Last visited

About leahcim

  • Rank

Recent Profile Visitors

136 profile views
  1. To update, I've got it working now by parsing the available MacOS UTIs and mapping the extensions to UTIs. Little bit of extra work, but it works flawlessly and allows me to search in files of a specific file type.
  2. Thanks @Vero! Yes, UTIs can be dragged & dropped which is very convenient - however, in my case I want to make it dynamic so that I can specify the extension from Alfred's input box. Therefore, I cannot pre-set any extension filter in the File Filter node, but need to dynamically retrieve it from the input and then set it in the node via a JSON update. And the only solution I've found is to parse the available UTIs from MacOS.
  3. Hello all as I understand the default in keyword allows to search contents of a file, but cannot be limited to a certain extension (all parts of the search expression will be used to match against the contents) the File Filter node in custom workflows allows to filter by extension, but requires to provide the UTI and does not allow to simply search for ".txt" as an extension. Determining the list of available UTIs and their respective extensions is not trivial Is my understanding of above behaviour correct?
  4. I agree, that would be my preferred solution as well - or, even better, cycling through all matches. Same as in most terminals.
  5. To be sure, using tab to autocomplete only works if there is a single matching result - do you have only one result? e.g. when typing ~/Appl
  6. For all fellow ClickUp users - let me know in case of questions or if you have ideas to improve this workflow! ClickUp 2.0 Alfred Workflow This workflow allows you to use Alfred to quickly add tasks and search tasks within ClickUp 2.0. Note: This is the first public release - bugs may be numerous. Let me know if you find any! Installation & Requirements For this workflow you need ClickUp 2.0 (will not work with 1.0) Alfred 4 with a Powerpack license To install, download the latest release and open the .alfredworkflow file. Configura
  7. Yes, that is what I meant - the user could "change" his input i.e. repeat it by typing anything. I found out about the checkbox as well, its effect is well hidden! Thanks a lot, all is working now - API gets called only once, user is redirected to web page where their input is displayed.
  8. Good point. Having a Keyword node and a Script Filter node would mean that the user enters the keyword and text the input is passed to the Script Filter the user is still able to enter/change his input, causing the Script Filter to be re-started for each keystroke, causing multiple callouts Is there a way to block the input field in the Script Filter? I've tried setting an environment var that is changed when the script is called, however as the Script Filter is restarted with each keystroke, also this var's value is reset...
  9. Understood. Thanks, @vitor. I will give it a try! However, this also means that. I have to go with the 'hacky' way of using a dot to end the command. I'll have to try whether I can add a high delay (e.g. 5 seconds) but still allowing the user to press enter immediately. That might do the trick.
  10. Thank you, @vitor! I have seen that as well. Unfortunately, that seems a bit cumbersome from a user's perspective - as a user, I simply want to hit 'Enter' once I am done entering my text. As a developer, I don't know whether the user is done - or just waiting a few seconds. Good to know! That works, good to know as well - however, this also means that my Script Filter no longer has any input to display the list item, as {query} is now empty. Is there a way to have the Script Filter use the {query} to display a list item, but without populating Alfred's in
  11. I am looking to implement a workflow that calls an API after a user has entered some text. In order to not reach certain API call limits, the callout should only be performed once the user presses Enter (one time - not after every key stroke). The webservice will then return a response to be displayed to the user as an Alfred list item. The user may press Enter on the displayed list item to open a certain URL that the API responded with. This is the concept I came up with (note: No workflow that I can export yet): 1. [Keyword] User enters a keyword and then some text (e.g. 'mywf so
  12. Thanks @deanishe, that works! It seems to be an issue with Alfy then, as it prevents me from witing to STDERR instead of STDOUT. The following works: console.error('TEST1') // Writes to STDERR, not shown in notification console.error('TEST2') // Writes to STDERR, not shown in notification console.log('TEST3') // Writes to STDOUT, shown in notification But once I import Alfy it no longer works: const alfy = require("alfy"); console.error('TEST1') // Writes to STDOUT as JSON console.error('TEST2') // Writes to STDOUT as JSON console.log('TEST3') // Writes to STDOUT
  13. Hi @deanishe, thank you! Sure, I've uploaded the workflow here: https://gofile.io/?c=QkslSS Regarding Alfy, the example is similar even without, just using NodeJS' standard console.log(): console.log('TEST1') console.log('TEST2') With this code, while indeed no JSON structure will be displayed (apparently alfy.output() is only for JSON structures, unlike alfy.log()), the notification will still display all console.log() statements at once: TEST1 TEST2. How can I only pass TEST2, i.e. the last log element to the notification?
  14. Hello I seem to have trouble understanding how outputs from scripts are digested by follow-up nodes. I have the following example: A NodeJS script (index.js) that is executed when entering a keyword (cut <text>) The script uses the Alfy package (same issue without the package) The script uses alfy.output('TEST') to write to STDOUT (same as console.error()) The script then passes its output on to a Post Nofification node which shows {query} The notification is displayed as: { "items": [ { "title": "ABC\n", "s
  • Create New...