Yeah, that seems to work, thanks!
On Mar 26, 2:31 am, Daniel <[EMAIL PROTECTED]> wrote: > You could make those aliases manually. Just create a subfolder of > Applications, say /Applications/Abbreviations, and put aliases in > there to common apps. You can even make the aliases with Quicksilver-- > There's an action called Make Alias In..., which will use the same > name as the original file but if you reinvoke QS that new alias will > be selected and you can rename it. Then reinvoke again, Cmd-R to > rescan and you should be good to go. > > On Mar 24, 9:21 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > wrote: > > > Really? That's a bit unfortunate since it would be a killer feature. > > The only thing that slows me down with QS is having to pause and > > remember the name of an application to launch it - being able to > > assign a mnemonic based on function rather than name would make the > > process much smoother and would be in keeping with the QS motto. > > > Of course I could assign a trigger to launch such apps but this > > feature is precisely for those apps (or files) that you don't use > > often enough to justify a trigger - and if you use an app that > > frequently you probably already know it's name by heart. > > > It doesn't sound like it would be a difficult feature to add either - > > even if for some reason QS only works by indexing file names, Assign > > Abbreviation could create file aliases for assigned abbreviations and > > index those. Piece of cake, right? > > > Scott > > > On Feb 14, 6:16 am, Howard Melman <[EMAIL PROTECTED]> wrote: > > > > assign abbrev only works if QS would have found the app if you had > > > typed the string. So you can't use it to make an abbrev irc for > > > Colloquy or ftp for Cyberduck. > > > > Howard > > > > On Feb 13, 2008, at 12:04 PM, metropical wrote: > > > > > every now and then certain mnemonics won't work. Even if I decrease > > > > score on the Finds. In most cases, QS won't even Find the item I'm > > > > looking for. These are always apps, some are Java. > > > > Any thought on a fix?
