> On 19 Jan 2016, at 16:15, Esteban Lorenzano <[email protected]> wrote: > > >> On 19 Jan 2016, at 15:23, Esteban A. Maringolo <[email protected] >> <mailto:[email protected]>> wrote: >> >> It turns the search field into a "kind of" command line interface, with >> #sen/#ref as commands. >> I love CLIs so I welcome it, but I think It "perverts" the search field and >> uses an awkward syntax. I prefer to type "senders" than to type a special >> character like #. >> >> I would prefer adding a suffix command so you search for 'do: senders' or >> 'do: implementors’. > > just that there is no syntactical way to know when you want senders or just > retrieve methods who start with do: and continue with keyword sen… etc. > that’s the reason from the hashtag (which is now a common symbol to > filter/tag like in twitter/facebook/etc.)
ah, btw… you can also do: do: #sen it does not have to be in front… just you need to use the hash :) > cheers, > Esteban > >> >> Regards! >> >> >> Esteban A. Maringolo >> >> 2016-01-19 10:43 GMT-03:00 Tudor Girba <[email protected] >> <mailto:[email protected]>>: >> Hi, >> >> With the latest GT integration, we also integrated the search for senders >> and references from the first step. >> >> Here is a detailed explanation about it, including what we still want to do, >> how it’s done, and how to discover what else is around: >> http://www.humane-assessment.com/blog/spotting-senders-references-with-gtspotter/ >> >> <http://www.humane-assessment.com/blog/spotting-senders-references-with-gtspotter/> >> >> <spotter-senders.png> >> >> Please let us know what you think. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "Problem solving efficiency grows with the abstractness level of problem >> understanding." >> >
