Andrew

@m3adi3c that's enough info thanks! I can see where that is happening now - I'll have this fixed today thanks
 
Andrew

@Overload119 The easiest way to achieve this at a generic level is to have a single separate hotkey defined to show Alfred with the currently selected text in macOS, and place the cursor to the left.
 
i.e. my Alfred hotkey is alt+space, but I have ctrl+alt+space (workflow hotkey trigger by itself) setup as the following, which puts Alfred in a state (cursor to the left) ready for me to type the keyword:
 

 
This way, you only need to remember two hotkeys - One for Alfred by default, and one for Alfred with selected text.
 
Cheers,
Andrew

Alfred 3.3 now has this option in the Alfred's advanced prefs - set Selection Hotkeys to "Restore previous clipboard item".
 
Cheers,
Andrew

@zachx08 There are a few ways you could do this.
 
Firstly, if you are using the "Launch Apps / Files" action, there is a checkbox at the bottom which toggles visibility. This will allow you to, for example, have one hotkey connected to this action with a single app, then use the hotkey to toggle between the app showing and hiding.
 
Alternatively, you could use some AppleScript to hide or minimise specific apps in the "Run AppleScript" action, e.g.
 
http://stackoverflow.com/a/3564215
 
Hope this helps
 
Cheers,
Andrew

@dennis.a It looks like you've actually spotted a bug - if you have fuzzy set to "Fuzzy capital letters" in Alfred's Advanced prefs, this works as expected, but when set to fuzzy from word boundary, the behaviour doesn't match the default results as intended.
 
I'm going to move this to the bugs forum and have it fixed for the next release
 
Cheers,
Andrew

@Srisri You'll need to configure the search fields for the filter to look at text content. Select the Advanced tab of the file filter config sheet and from the + button, select kMDItemTextContent. Remove the other items so it looks like the following:
 

 
Then, just use the file filter's keyword and search terms.
 
Hope this helps!
 
Cheers,
Andrew

@Srisri You'll need to configure the search fields for the filter to look at text content. Select the Advanced tab of the file filter config sheet and from the + button, select kMDItemTextContent. Remove the other items so it looks like the following:
 

 
Then, just use the file filter's keyword and search terms.
 
Hope this helps!
 
Cheers,
Andrew

@Overload119 The easiest way to achieve this at a generic level is to have a single separate hotkey defined to show Alfred with the currently selected text in macOS, and place the cursor to the left.
 
i.e. my Alfred hotkey is alt+space, but I have ctrl+alt+space (workflow hotkey trigger by itself) setup as the following, which puts Alfred in a state (cursor to the left) ready for me to type the keyword:
 

 
This way, you only need to remember two hotkeys - One for Alfred by default, and one for Alfred with selected text.
 
Cheers,
Andrew

@vitor perfect use case for clipboard history placeholder, and in fact, better than the new option I added in the Advanced preferences to buffer and restore in the Advanced prefs which can have minor memory implications.

My use case can now be accomplished in Alfred 3.3 b787 pre-release.
[{query}]({clipboard:1})

@S. Sasaki If you set the focus mode to compatibility in Alfred's Appearance > Options preferences, it works around this macOS bug.
 
Hope this helps!
 
Cheers,
Andrew
 
[moving to help]

The Alfred 3.3 pre-release b787 has now had some work done on the file actions, so this should be sorted

I've just been having a bit of a play to see if this is possible with a file filter, but it looks like it's possible with a direct metadata query in Terminal such as:
 
mdfind "kMDItemTextContent == '*This is a sentence*'"
 
I'm going to take a look to see if there are some improvements to the file filter, as this should theoretically be possible.
 
Cheers,
Andrew

Hi @abbood,
 
Alfred stores thes in a plain text plist in Alfred.alfredpreferences/preferences/features/websearch/info.plist so should be pretty easy to batch edit / change... but if you are doing lots of custom searches with the same / changing domain, it might be worth creating a workflow instead and using a variables for the domains.
 
Cheers,
Andrew

Ah yeah, this has slipped down in my tickets... I'll re-target it

@ghui there is no way at this point to automatically show variables which need filling. The best thing to do for now is put some info in the "About this Workflow" section to say something along the lines of: "Set your API token in the variables panel".
 
I'll add a note to have a think about "required variables" for a future release of Alfred
 
Cheers,
Andrew

Time to get passive-aggressive and submit a tutorial on how to convert smart quotes to dumb ones.

I agree with this and I actually raised a ticket the other day to look into reverting this and the other file actions (copy / move) back to telling Finder and using AppleScript. It would also re-sort the issue of moving apps to /Applications/ where permissions need to be elevated, and App Translocation fettling by Finder to take place.
 
Leave it with me, this is likely to be sorted.
 
Cheers,
Andrew

@Will-i-am not right now, but there will be in a future release of Alfred 3  ^A

@deanishe thanks for working that out - I'll get that sorted in the next release

I'll look into this, but for now, try switching Alfred to focus compatibility mode in the Appearance > Options preferences
 
Cheers,
Andrew

Alfred is in the ignore list by default (to prevent clashes when you use e.g. the snip keyword). You can remove Alfred 3 from the ignore list from the Features > Snippets prefs on the little cog to the right of auto expansion.
 
Cheers,
Andrew

@deanishe you can actually already do this if you prefix the type with a + for example:
+public.image ... will search the content type tree instead of the content type. This should be documented somewhere, I'll check tomorrow and add if it's not 
 
Cheers,
Andrew

@leonid thanks for finding this out and the link

@deanishe You are right, that would have been really difficult to explain without an example workflow!
 
If you update to pre-release b758, this should now be fixed