Jump to content

scottisloud

Member
  • Posts

    17
  • Joined

  • Last visited

Posts posted by scottisloud

  1. On 6/23/2020 at 10:44 AM, Vero said:

     

    @scottisloud Glad it's working :) Any chance you could elaborate on what issue you saw / what fixed it? It may help other users who are playing with Big Sur for the first time. 

    Sorry, totally missed out on the notification of this post. 

     

    The issue was that I had an absolute file path in the script that broke it. Used a relative path and fixed it up. So nothing on your end or anything specific to Big Sur, just me being silly! 

  2. It does run, but there are some issues with certain features (I'll try to document and report the issues appropriately. It may well be user error in some cases). I'm sure Andrew and Vero will get all these things sorted out over the beta period! It is a beta period after all! 

     

     

    UPDATE

    AAAAAAND it was user error. Minor tweak to my AppleScript and it fixed it up. 

  3. It's possible that that file type falls under a category you have excluded in Alfred.   

      

    Go to Alfred Preferences>Features>File Search and about 3/4 of the way down you'll see "Don't Show:" 

     

    I suspect if you have source files of plist files selected as "Don't Show", that particular file may not show up.  

     

    Another place to look is Features>Default Results  and check your search scope. It is possible that while Spotlight has indexed the directory, that it has not been included in Alfred's search scope. 

  4. Loving all the new features! They are all very exciting. 

     

    Just wanted to echo what quoquus is saying. There is a counter-intuitiveness to the history feature at the moment. When the user is browsing the history and pushes "down", I suspect they are expecting one of two potential outcomes.

    1) navigating the reverse direction in the history

    2) navigation of the currently displayed search results. 

     

    Currently the functionality is in line with 2. But the problem, as I see it, is that this immediately pushes the user out of the history, so continued pushing of the up arrow after pushing the down arrow does not result in navigating to the next history item, it scrolls through the search results, circling back from result 1 to result 20.  

     

    Perhaps it could be configured so that if the user arrows to the first search result after a downward arrow press while browsing the history, the user can continue through the history instead of being taken from result 1 to result 20. 

     

    Alternatively, what about choosing an alternative keystroke? Page up/down or fn-up arrow/down arrow? 

     

    either that or we can all just learn to adapt!

×
×
  • Create New...