Jump to content

Search the Community

Showing results for tags 'file type'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Alfred 3
  • Make the Most of Alfred
    • Discussion & Help
    • Bug Reports
    • Alfred Feature Suggestions
    • Themes
  • Alfred Workflows
    • Share your Workflows
    • Workflow Help & Questions
  • Alfred v2 Themes
  • Alfred Remote for iOS
    • Alfred Remote Discussion & Help
    • Remote Connection Troubleshooting

Categories

  • Articles
    • Forum Integration
    • Frontpage
  • Pages
  • Miscellaneous
    • Databases
    • Templates
    • Media

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Twitter


Website URL


Jabber


Location


Interests

Found 3 results

  1. Since this is what I think the standard way to set an environment variable from a Script Filter, I think this should be working, but feel free to move this post to the feature request if this the normal behaviour and not a bug. When building a workflow that works with files and folders, I like to allow to run actions on those files/folders. So, since the File Action is made for that, I like to just activate it on my script filter output item by using my File Action shortcut (sets to cmd-cmd in my case). However, when I want to set an environment variable inside the Script Filter, then the File Action shortcut doesn't work anymore even if "type" is set to "file" in the JSON. Since this environment variable is used when I normally activate the selected item on my workflow by pressing enter and could change based on which item of the Script Filter is activated, I need to set it inside the Script Filter and not after or before, but would like to keep the default behaviour of the " 'type': 'file' " item. Here is a workflow to demonstrate this: https://nofile.io/f/xZGFinuS44I/Script+Filter+-+File+Type+with+File+Action+-+Test.alfredworkflow Let me know if something isn't clear enough! Best!
  2. I upgraded to OS X 10.10.3 and now Alfred cannot find my markdown files. I seemed to try everything in this guide http://support.alfredapp.com/kb:indexing, but maybe there's something I missed. Here's what all I tried. 1) OS X Spotlight Preferences > Privacy. No folders were listed. I added the folder and removed it. 2) OS X Spotlight Preferences > Search Results. All boxes are checked 3) Alfred Search scope is set to the right folder. I removed and re-added the folder. 4) File permissions: I set all the files in the folder (and the folder itself) to Chmod 777. 5) I rebuilt the OS X spotlight index ("Rebuild OSX Metadata"). It took over an hour, but I let it complete fully. Spotlight actually sees the files just fine but Alfred doesn't. 6) File Types: I removed and re-added the markdown file type in Alfred (Features > Default Results > Advanced) 7) I refreshed the Alfred cache ("reload") If I type "find" or use the shortcut ( ' ), the file shows up, but just typing the filename doesn't pull up anything. Here is an interesting hint - when I enable "Unintelligent (Search all file types)" in Features > Default Results, the markdown files show up! Not sure what is happening, though... Alfred v2.6 (374) OSX 10.10.3 Thanks.
  3. For me it would be great to run a special File Action for "*.sublime-project" files just by pressing enter, without explicitly selecting a File Action using right-arrow or a workflow prefix. Description: 1. find a ".sublime-project" file using the normal fuzzy File Search 2. hit enter 3. run my custom sublime File Action / workflow Alfred can already move your custom File Actions to the top with "Sort action by last used per file type". An extra checkbox for implicitly executing the top-most action just by pressing enter is maybe enough to enable this feature. This is helpful when using Alfred as a cmd+tab complement to switch between open files and applications. Example: Switch to chrome: "chro...[enter]", then switch to a sublime project: "myproj...[enter]". (The latter would run my custom workflow.) Kind regards, Carl PS I have found a workaround by changing my "*.sublime-project" files in OSX to always open with a home-made application running some additional scripts when these files are opened.
×
×
  • Create New...