The essence of my suggestion was to not do it by default but to provide a simple way for the user to say "yes, I really want you to search for this substring anywhere" rather than forcing it on everyone.
SDR On Mon, Aug 27, 2012 at 11:24 AM, Stephan Beal <sgb...@googlemail.com>wrote: > On Mon, Aug 27, 2012 at 7:18 PM, Scott Robison <sc...@scottrobison.us>wrote: > >> fossil co --glob 154 >> >> Though I'm not personally looking for this functionality myself so not >> having it as an official feature doesn't bother me. > > > > FWIW: as Richard said, it's _technically_ easy, but brings with it both > philosophical and usability concerns. Fossil would need a way of allowing > the user to disambiguate, e.g.: > > "possible matches: > 1) ... > 2) ... > type number to continue..." > > and that type of feature would then arguably need to be added to other > commands which deal with branches/tags. > > IMO a custom shell-based solution is the proper place for this. If it can > be demonstrated that this is feasible, i'll stop being pessimistic about it > ;). i suspect, however, that any attempt at doing so would reveal worms > which haven't yet been mentioned. > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > http://gplus.to/sgbeal > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
