@Sesquipedalian: Yes, I said that above. Actually running an exec outside its package *does* usually work, but it opens up a Terminal window that, if closed, closes the app. It also does other weird stuff. Not an option.
What about writing a shell script like: #!/bin/sh open /Applications/Firefox.app calling it "browser," putting it in the mnemonics folder, and using the "run" (*not* in Terminal, but the plain old "run" with an icon that looks like an executable file) action on it? The default action, then, should really be set to "run" for that item, which basically means arrowing down to it, clicking on the little dot and selecting "make default." *Don't* type anything or it'll only make it default for that string. If that action isn't there, go into the prefs and enable it, but make sure you get the right one (the one with the black glass with green "exec" text on it--the same icon the system uses for executable files). I tried that, and it does seem to work. Doesn't even require any actual use of the Terminal. On Mar 28, 12:59 pm, Howard Melman <[EMAIL PROTECTED]> wrote: > I was thinking to the .app, and of course, yeah, no hard links to > directories. Time Machine added this but not for general consumption > to avoid path loops. > > Howard > > On Mar 28, 2008, at 12:53 PM, Sesquipedalian wrote: > > > > > No good. Running an executable outside of its app package will not > > work, and that in effect is what a hard link to the executable would > > amount to. So hard links aren't a viable workaround. > > > On Mar 28, 12:39 pm, Sesquipedalian <[EMAIL PROTECTED]> wrote: > >> Hard links cannot point to folders, so far as I know, and .app > >> packages are folders. The only way this might work is if it pointed > >> to the executable within the .app package. > > >> On Mar 28, 11:01 am, Howard Melman <[EMAIL PROTECTED]> wrote: > > >>> Hard links seem worth a try. I don't see how QS would be able to > >>> see > >>> the original name using them. > > >>> Howard > > >>> On Mar 28, 2008, at 10:56 AM, Daniel wrote: > > >>>> @Howard: Yep. Sometimes that's sensible behavior, right now it's > >>>> just getting in the way. I wonder if QS would do the same thing > >>>> for > >>>> *hard* links. > > >>>> ...Which don't quite work, because opening an executable opens a > >>>> Terminal window and ties the app to that window. Not good. One > >>>> could > >>>> make shell scripts that just do an "open /Applications/ > >>>> Firefox.app", > >>>> which would free the app from the Terminal, but then you'd have to > >>>> launch them using the "run shell script" action. I suppose you > >>>> could > >>>> set "run shell script" (NOT "in terminal") as the default action > >>>> for > >>>> executable files, and that shouldn't affect anything else that I > >>>> can > >>>> tell. This is all starting to get very complicated and inelegant, > >>>> though--you may want to just give up on the idea for now and hope > >>>> the > >>>> next version of QS includes the feature. > > >>>> I can't think of anything else at this point that might work--your > >>>> description of what you did was very clear and complete, and > >>>> Howard is > >>>> right that QS is following the alias before indexing. > > >>>> On Mar 27, 3:57 pm, "[EMAIL PROTECTED]" > >>>> <[EMAIL PROTECTED]> > >>>> wrote: > >>>>> @Howard: I just mean that the custom mnemonic triggers assigned to > >>>>> aliases are not remembered across sessions. Everything else in QS > >>>>> including the custom File & Folder Scanner is correctly saved. > > >>>>> @Daniel: I created a folder under ~/Applications/QS Mnemonic > >>>>> Aliases/ > >>>>> and put a couple of aliases in there and named them with the > >>>>> mnemonic > >>>>> I wanted to assign. Then I added a new File & Folder Scanner under > >>>>> Custom in the QS Catalog and selected that folder. Under Source > >>>>> Options I have Include Contents: Folder Contents chosen, a depth > >>>>> of 1 > >>>>> selected and Omit source item checked. After rescanning the > >>>>> catalog > >>>>> it > >>>>> shows 2 items, and the Contents info panel shows my 2 aliases - > >>>>> actually it shows the original application and file that the > >>>>> aliases > >>>>> pointed to rather than the aliases themselves. > > >>>>> The catalog and contents are persisted across sessions. Double > >>>>> clicking the icon in the Contents panel opens a QS window with the > >>>>> source as subject. From here I right-click the source icon and > >>>>> select > >>>>> "Assign abbreviation" from the Actions menu. Testing the > >>>>> mnemonic at > >>>>> this stage does not work. Repeating the procedure and choosing > >>>>> "Show > >>>>> source in Catalog" from the Actions menu opens the Appications > >>>>> catalog > >>>>> for the application alias, and the file alias opens in User > > >>>>> Recent > >>>>> Items > Recent Documents Catalog. > > >>>>> By bringing up the "QS Mnemonic Aliases (Catalog)" as the QS > >>>>> subject > >>>>> and navigating inside it to the items and assigning an > >>>>> abbreviation > >>>>> simply does not work no matter how many time I assign it and > >>>>> rescan > >>>>> the catalog. However by bringing up the "QS Mnemonic Aliases" > >>>>> folder > >>>>> (not catalog) as the QS subject and navigating inside it to the > >>>>> items, > >>>>> assigning an abbreviation and rescanning the catalog does work > >>>>> from > >>>>> that point on, until QS is restarted at which point they are lost. > > >>>>> Thanks, > > >>>>> Scott > > >>>>> On Mar 28, 5:08 am, Howard Melman <[EMAIL PROTECTED]> wrote: > > >>>>>> I've been following this thread with curiosity. My experience > >>>>>> trying > >>>>>> to use OS X aliases for this was that QS indexed not the alias > >>>>>> but > >>>>>> what it pointed to, which made the hack not work. You can > >>>>>> select the > >>>>>> catalog source, hit the i button to open the drawer and look in > >>>>>> Contents to see what it's scanned. > > >>>>>> Say "settings are lost" is a little to vague for me to help. > >>>>>> Settings > >>>>>> are stored in: > >>>>>> ~/Library/Preferences/com.blacktree.Quicksilver.plist > >>>>>> ~/Library/Application Support/Quicksilver/ > >>>>>> Provided you have write access to these files and folders QS > >>>>>> should > >>>>>> have no problems remembering settings. When you say "settings" > >>>>>> do > >>>>>> you > >>>>>> mean all settings or just one thing in particular and if so what > >>>>>> specifically? > > >>>>>> Howard > > >>>>>> On Mar 27, 2008, at 11:24 AM, Daniel wrote: > > >>>>>>> I'm not sure what to say, then. Make sure, of course, that the > >>>>>>> scanner is set to include folder contents. Also, click on the > >>>>>>> "contents" tab in the inspector pane for that scanner and see if > >>>>>>> there's anything there. Make sure the scanner is checked, > >>>>>>> etc. If > >>>>>>> you can ever see the aliases, do a "show source in catalog" on > >>>>>>> them > >>>>>>> and make sure it shows as the new scanner and not the default > >>>>>>> Apps > >>>>>>> one. Maybe try moving the QS preferences to the Desktop, > >>>>>>> remaking > >>>>>>> that scanner and seeing if it works now. I've been having > >>>>>>> similar > >>>>>>> problems, but I've usually been able to fix them basically by > >>>>>>> trying > >>>>>>> stuff over and over until it worked. QS is sorta "stubborn" > >>>>>>> sometimes.
