<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Not so much combinations, just simply a tree of commands -> option names<br>
-> option value enumerations. Obviously only the enumerations are<br>
particularly completable; either fixed ones, or ones based on some<br>
running data list (channels/nicks/etc...)</blockquote><div>The problem is where there is interaction between options in the general case. Flags changing what are valid targets, etc. But yes, I suppose for a lot of things that may work just fine.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">That was roughly where I was aiming, possibly via some laziness. Perhaps<br>
roundtrip is "good enough" to lazily populate the options to a command<br>
the first time the command's name gets completed?<br>
<br></blockquote></div>The problem is that lazy population will make the UI feel "sluggish." If we do this we should demand it all upfront and populate/update the information as we would anything else, or turn it off entirely. The "middle case" where bandwidth is scarce but roundtrips are cheap/fast doesn't seem terribly common. If anything, you usually have the case where bandwidth is cheap and plentiful but you have high latency (satellite broadband, "good" cellular links.)<br>
<br>To see exactly what I mean about "sluggish," use modern bash intelligent completion on an older machine. It's absolutely maddening.<br>