On Jul 4, 2012, at 2:58 AM, Patrick Robertson wrote: > This is an interesting one, and perhaps one of Quicksilver's biggest > shortcomings: there's no blurring between Text Mode and 'normal' mode. > Perhaps an idea could be to have a 'text mode' item in the results list for > ALL searches.
There is a (command) preference "Switch to text mode if no match is found" On Jul 5, 2012, at 9:58 AM, Rob McBroom wrote: > Once it’s selected, how would you edit it if there’s no text mode? :-) Agreed. > What about a preference to require holding ⌃ or ⌥ when hitting . to enter > text mode. So . by itself would act normally? ⌥ would be the better choice as many apps use it to enter odd characters (⌥ ↩ being the most common one I hit). Still I think this is confusing. I think less than 10% (probably less) of mac users know of this. While I agree that QS has a lot of prefs, I think non-discoverable key combinations are worse. > But this doesn’t seem necessary to me. As Jon pointed out, just a couple of > letters alone should be enough to find just about anything. I agree. This has come up on the forums over the years and the answer, don't type . usually is sufficient (and faster). Still I have to agree with this: On Jul 6, 2012, at 8:44 AM, David Rees wrote: > Thanks Jon, its a good point that space is essentially a multi-character > wildcard like ".*"/"?*"/"*" (depending on your preferred regexp), but what I > was hoping for is a single character wildcard like "."/"?". > > For better or worse I have used period is a separator in a lot of my > documents. So I have files like dev.NOTES.docx and devices.NOTES.docx. I want > to be able to search for thing like ".NOTES". Since objects could be lots of > things beyond documents (texts on shelf) I was hoping there was a way around > a normal character like period acting like a command. Its pretty unusual in > my experience to not have an escape character for special characters in a > search pattern. Then again, time and time again, users don't grok search patterns. Maybe globbing but not regular expressions. Escaping in this case seems worse than skipping over the . when typing. And since QS does matching, there isn't a need for wildcard. E.g., "devnotesdocx" shoudl still find that document. Still I agree that different people (and organizations) use different conventions for file name separators. Maybe the better solution is to make a QS preference for the character to enter text mode and default it to ".". Those that use . commonly can change it to - or something. Howard -- You received this message because you are subscribed to the Google Groups Quicksilver group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at https://groups.google.com/d/forum/blacktree-quicksilver?hl=en
