Finder selection shortcut (Cmd-G) doesn't work #510

Closed
djradev opened this Issue Oct 23, 2011 · 22 comments

7 participants

@djradev

Open Finder, select a file, open QuickSilver, hit Cmd-G -> enclosing folder gets selected instead of the file

OS: 10.7.2, QuickSilver ß61

@pjrobertson
Quicksilver OS X member
@djradev djradev closed this Oct 23, 2011
@djradev djradev reopened this Oct 23, 2011
@djradev

Interface -> BazelHUD

Prefs→Extras→'Pull selection from front app instead of finder'?" -> Not Selected

Reproducible with every folder (initially I noticed it with Downloads folder)

Thanks for the great job you are all doing!

@pjrobertson
Quicksilver OS X member
@djradev

Just tried and I can reproduce it with Bazel and Primer as well. For me at least the problem is not with BazelHUD.
Is there some hidden setting how QS gets current selected item in Finder?

@christiankn

I can reproduce this bug with "Pull selection from front..." enabled

Occurs with both Bezel and Primer HUDs.

With it disabled it will only grab the selected item of the desktop, regardless of how I select an item in Finder. (Mouse, opening a folder with QS or navigating to it with the keyboard.)

@pendolino

this has been a persistent problem for year. i've noticed that it goes away for a while with clean installations of OSX and/or Quicksilver (have not figured out the pattern or cause exactly yet) but it sucks when you dont have this useful feature.

@skurfer
Quicksilver OS X member

This has come up before. See #409.

@stevenbagley

This will reproduce the bug every time.
1. Find a file using spotlight.
2. Hit command-return to reveal file in its folder.
3. Invoke Quicksilver, then command-G.

This is with OS 10.7.3, QS 3923, using Bezel (built-in). It seems to happen regardless of the state of the "Pull selection from ..." option. Curiously, changing to a different command interface seems to clear the bug, but it then returns after the first iteration through this cycle of commands. I would love to see this fixed as it is driving me slowly insane.
--Steve

@pjrobertson
Quicksilver OS X member

I cannot reproduce your problem @sbagley.

Is it possible any of you are using non QWERTY keyboard i.e. a different keyboard layout?

If so, then this issue has been fixed by 096b4a1 and will be out in the next version of Quicksilver

@stevenbagley
@pjrobertson
Quicksilver OS X member

Thanks again @sbagley for the detailed steps to reproduce the problem. A complicated one, but it sure is possible!

Looking into it, it appears to be a limitation with Finder's AppleScript functions.
Having said that, we should probably move over to using a newer method of implementing AppleScripts (Scripting Bridge), and I have flagged this up with our resident Scripting Bridge expert @skurfer ;-)

Hopefully we can get it fixed soon. As a workaround, I suggest you use the ⌘⎋ shortcut which will pull the currently selected item into Quicksilver without having to invoke Quicksilver itself. It works in any application and can also be used for things like text etc.

@pjrobertson
Quicksilver OS X member

An update, as @skurfer has suggested in #409, this could best be fixed by altering the ⌘G shortcut to use the same method as the ⌘G shortcut.

Hopefully this will be fixed when that one is

@stevenbagley
@pjrobertson
Quicksilver OS X member
@skurfer
Quicksilver OS X member

Having said that, we should probably move over to using a newer method of implementing AppleScripts (Scripting Bridge), and I have flagged this up with our resident Scripting Bridge expert @skurfer ;-)

Don’t think I haven’t dreamt about it, but that will be quite a project. :-) Some advice in case someone gets to it before I do: Manually generate the headers for the various applications instead of following the normal process of having it generated during build. I’ve found that referencing the application in a project makes “find in project” pretty awful. Not so bad for a plug-in with a few files, but it would be a nightmare for Quicksilver itself.

@pjrobertson
Quicksilver OS X member

I have been looking into this issue, and it appears to be a bug with OS X 10.7 and 10.8.

See this list thread and this openradar report

It appears that we are either at the mercy of Apple, or we try and find another way of reliably getting the selection from Finder… which I don't think exists.

I've looked into trying to 'trick' Finder into refreshing its windows and its current selection, but unfortunately nothing seems to exist.
I suggest that as many people as possible file a bug report at https://bugreport.apple.com in the hopes that Apple will fix the problem

@skurfer
Quicksilver OS X member

There was another ugly fix mentioned in the e-mail thread. Before trying to get the selection:

set win to make new Finder window
close win

And yet another mentioned in the radar report. I'll go open a report on it myself.

Update

Opened 12461795

@pjrobertson
Quicksilver OS X member
@pjrobertson
Quicksilver OS X member

OK, having looked more into the options of using a 'workaround' with Scripting Bridge, no ideal solution has presented itself.
I will close this issue now as a 'will not fix', hoping that Apple will do something about it soon.

Having said that, we will be taking steps to simplify the finder selection proxy somewhat. See #485 for more info

@pjrobertson pjrobertson closed this Oct 9, 2012
@lgarron

This issue appears to be the central one that gets mentioned any time the problem comes up. I've created a wiki page documenting what I could: http://qsapp.com/wiki/Finder_Selection

@skurfer
Quicksilver OS X member

Thanks for the detailed write-up, @lgarron.

@pjrobertson
Quicksilver OS X member

I can confirm that I haven't had any problems in Mavericks... yay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment