Andrew

Hmm I'm going to have to investigate why I made it AppleScript only in there, it may just be a completely legacy thing. I'll add a note, and if there is no significant reason, then I could likely add in arbitrary scripting.

@deanishe I understand that... and thought I had conveyed why in my reply in the 3 bullets. His hotkey takes the Selection in macOS (arbitrary selection); When text is selected in Alfred's search field, THAT is what is copied to the clipboard when you use ⌘C (which Alfred uses for selection in macOS).

@ladychili check the macOS Security & Privacy > Privacy > Automation settings to ensure that Terminal / iTerm is selected for Alfred. If it is, then try un-ticking and re-ticking these. You may also need to check your specific integration with iTerm in Alfred's Features > Terminal is correct or up to date. Cheers, Andrew

There were a couple deliberate design decisions I made with this behaviour, which you've already noticed: When showing Alfred with the previously typed text, this is highlighted automatically so that it can easily be overtyped. Selection in macOS works by using ⌘C in any app, it doesn't matter the context, e.g. a textual path in Terminal will work as well as a file in Finder. For intrinsic usability, if there is a text selection at any point in Alfred's input field, ⌘C will copy this instead of the highlighted result. The selection in the hotkey you are using is disconnected from and agnostic of the underlying app, which is why it can't work like one of the built-in action modifiers. To clarify, you use the hotkey, it simulates ⌘C and uses the result. It just so happens that this also works within Alfred's own window because Alfred presents the results as copyable. To "work around" this issue, you could always press the left arrow before using your hotkey to select the file. This would move the caret to the left of the typed query (while not invoking the default right arrow actions panel), then there is no selection in the input field, allowing for ⌘C to take the selected result. As for a behaviour change, I'm not overly keen on arrow down automatically clearing the selection as suggested. This wouldn't be consistent behaviour across Alfred, and wouldn't match macOS built-in behaviour (e.g. Spotlight). This would also be inconsistent for the top result (without pressing the down arrow) vs subsequent results after pressing the down arrow and results being cleared. In your workflow, you could setup the following which would achieve what you need: Hotkey > Dispatch left arrow > Dispatch ⌘C > Delay 0.1 > Arg/Var putting {clipboard} into Argument > ... I'll have a bit of a think about some other workarounds to this issue, but it's not a common problem as I can't remember if this has come up before. Cheers, Andrew

@vitor these are configured in Alfred's Advanced prefs, you can disable "Action visible results" and also configure the "Reveal in Finder" shortcut which should work in default results and navigation. Cheers, Andrew

@Gee Did you remove Alfred from the macOS Accessibility prefs, and re-add back again?

@Gabriel_A the cog and sorting options were added in Alfred 4, I suspect you're still running Alfred 3. I can see you've already obtained your v4 license, so you'll need to update to Alfred 4 if you want this option.

@abdulrahman sahmoud Have you installed a Sublime extension, or have sublime configured to have concealed or transient clipboard interactions? Alfred discards concealed or transient data by design. [moving to discussion and help]

@Gabriel_A the sorting options in navigation mode are from the little cog in the bottom right of Alfred's File System Navigation window. https://www.alfredapp.com/help/features/file-search/#file-nav

Thanks! I may give this a go

@andersennl would you mind sharing a little more info about how you're achieving this, as it may help others. Are you using Synology Drive Client?

Ah I missed this first time it was posted, totally useful. I'll sneak it in for the next 4.0.9 build

@aduco macOS is extremely clever with the way it manages memory, and force "freeing" ram on your Mac will undo all the benefits which come for free (no pun intended) Essentially, macOS will hold things you'll likely need in caches and fill up as much unused ram as necessary to keep things running as fast as possible. When this ram is needed, it will be made available if it's being used by these caches. By force freeing the memory (e.g. using purge in Terminal), you'll likely slow your Mac down.

@Acidham sorry about the delay on replying, thanks for spotting this! I've now fixed this in the 4.0.9 b1142 pre-release

@Gee Sometimes, there can be permissions issues after restoring from Time Machine. Try quitting Alfred, then removing all the permissions granted in the macOS Security prefs, then adding them back again. Also try repairing the permissions on Alfred's preference files using step 1 in this guide: https://www.alfredapp.com/help/troubleshooting/preferences/ Cheers, Andrew

Note: I've now put this out as a pre-release, the link above has been removed

Thanks! That sounds promising

@andersennl Alfred keeps live references open to files in his preferences, so expects them to both be always available, and fast. As such, it's not ideal to set the sync location to a remote volume, as if this drive were to not be available on startup, or disappear during Alfred's operation, then you could expect some issues in Alfred. One option could be to setup rsync between Alfred's preferences and your Synology NAS. This way, Alfred's preferences would be local, but you could rsync a copy out to the Synology every time a preference changes. Cheers, Andrew

If you're following this thread, and haven't yet seen my reply in the following thread with a build to try.

@hazephase try tapping space on the file to quick look that file. Alternatively, if all of the files are in the same folder, you could use Alfred's file navigation mode, e.g. paste ~/Downloads/ into Alfred.

@PaulGuy in Alfred, use cmd+backspace to clear the entire query. There is no way default way to reconfigure backspace to delete the entire query by itself. Cheers, Andrew

For people experiencing this issue, would you please quit Alfred and replace the app with the one in the following dmg: NOTE: LINK REMOVED - This is now in 4.0.9 b1141 pre-release available from Alfred's Update preferences. With this build, if the number of screens has changed when attempting to show Alfred, the main window is released and re-initialised from scratch. I'm hoping that this will have the same effect as restarting Alfred, which has been reported to have fixed the issue for some. Let me know how you get on, and if you're able to reproduce the issue with build 1139. Cheers, Andrew

@peppy-blue-wolf I'm currently looking into a workaround to this issue, follow this thread for updates:

@alexbet Quit Alfred and delete the folder you listed (/.../Caches/Metadata/1Password/), then restart Alfred and he will look elsewhere for the data. If Alfred can't find any other locations, this could be the correct folder location, just bad permissions on that folder meaning 1Password can't change the files.

@alexbet that looks like the correct locaton. To double check that Alfred is looking at the correct location, with Alfred's preferences quit, disable 1Password 3rd party integration within 1Password's Advanced prefs, then launch Alfred's Preferences to Features > 1Password. The list should now be empty with a little red error at the bottom. If so, re-enable 3rd party integration in 1Password, then re-launch Alfred's Preferences and they should be back. Let me know how you get on with that, then we can take if from there.