Re: [Gzz] ``search_bindings--benja``: Convenient bindings for full-text search

[Tuomas Lukka]

On Sat, Nov 02, 2002 at 05:19:28PM +0100, Benja Fallenstein wrote:
> Tuomas Lukka wrote:
> 
> >On Sat, Nov 02, 2002 at 03:25:43PM +0100, Benja Fallenstein wrote:
> > 
> >
> >>I don't know yet; search policy objects need an own PEG. However, we can 
> >>use StringSearcher for now (which means passing all the so-far typed 
> >>ones).
> >>
> >>The problem is that we want to be able to have e.g. tab completion 
> >>depending on the policy object.
> >>   
> >>
> >
> >Ahh, that's an excellent point. Please make this explicit in the PEG.
> >
> >But are there others than tab completion? Would be nice not to force
> >StringSearchers to have an user interface.
> >
> 
> Hm, replacement: enter an abbreviation and have it expanded to a whole 
> word. This is not Tab completion because it doesn't only add characters.
> 
> I just want to ensure that there's some way to tweak these things 
> easily, because I don't feel able to decide which way it should be, not 
> even which way it should be by default, at this time. So I want this PEG 
> to only specify how to enter and exit search mode, but leave what 
> happens inside search mode to future pegs with possibly conflicting options.

Oh, yes, but specify in the PEG that this is what we want to do.

For example, an "Issue: should we pass things to search policy always as strings
or something else? RESOLVED: Not defined yet, as we may want ... ... ..."

The point is that the PEG should not only say what, but also why.

        Tuomas