[Circle-dev] Tab-complete in frontends

[Paul LeoNerd Evans]

On Wed, 25 Mar 2009 20:03:37 -0500
Kiyoshi Aman <kiyoshi.aman at gmail.com> wrote:

> It would be convenient (and, I feel,
> more optimal) if the client (which already knows all the objects)
> could be intelligent enough to assemble tabcompletion trees as data
> comes in for other things and as the user tabcompletes.

Well, I think this was my point. The frontend doesn't know _all_ the
objects.

It can be told easily for, say, an IRC channel, to use the names list.
That's easy. But consider completing on command options:

 /win<tab>

(oh quick, we need to know all the command names. That's just a list,
right?)

 /window cl<tab>

(hrm. OK. Now we need to grab its subcommands. Better instead have an
entire tree of them)

 /window close -t<tab>

(ah. Now they have options. OK. Lets get those as more trees)

 /window close -type=q<tab>

(some of these options appear to have enumerated arguments. We should be
able to complete on them too)

 /window close -type=query


It's not quite as simple as just a flat list of names here :)

-- 
Paul "LeoNerd" Evans

leonerd at leonerd.org.uk
ICQ# 4135350       |  Registered Linux# 179460
http://www.leonerd.org.uk/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.leonerd.org.uk/pipermail/circle-dev/attachments/20090327/9aad8c75/attachment.pgp>