thinklad
-
Posts
4 -
Joined
-
Last visited
Content Type
Blogs
Gallery
Downloads
Events
Profiles
Forums
Articles
Media Demo
Posts posted by thinklad
-
-
As OneDrive for Business is moving the default location from ~ to ~/Library/CloudStorage/ I added that location to the search scope so I can quickly open folders in Finder from an Alfred search (as by default I understand the ~/Library/ folder is excluded from search results).
However that is still not returning any entries, even after I deactivated and reactivated 'Folders' from the Alfred default results. I can find those same folders from within Spotlight.
Is there something specific I should be doing to have access to these folders in ~/Library/CloudStorage/ ?
-
It might be that you haven't yet "taught" Finder how you like your new windows.
You have to open a new Finder window, make it look just the way you want (size, view, sorting etc.) and then close it again without using the window at all (opening files/folders, navigating between folders etc.).
After that, all new windows should look that way regardless of how they're opened.
No, I did teach Finder to remember my preferred view settings. So whenever I create a new Finder window, I have no issues. It's only when I invoke a folder from Alfred that it falls back to a small window size, not aligned with my preferences.
-
Hi there,
I just set up Alfred on my new iMac, syncing settings from my MacBook Pro install.
I can open new Finder windows with my preferred view options (see here) when invoking it from the Finder (e.g. new window with ⌘N). The window size, list ordering (in my case, reverse chronological) etc. is how I want it to be.
However when I open a folder through Alfred (which I do countless times a day), it will always revert to a small Finder window size and alphabetical ordering. I don't recall having the same issue on my other machine.
Does anyone know what could be the issue here?
Folder search scope in ~/Library/ not working
in Discussion & Help
Posted
Looks like I needed to be a bit more patient — the issue eventually resolved itself (unclear if that's because of another restart linked to the macOS 12.1 upgrade); thanks though!