> This brings the completions system into the browser-object system, and > if we further find a means to switch browser-object-classes during an > ongoing interaction, that will cleanly solve the issue that David > raised, plus switching between any of the existing > browser-object-classes. For my part, I'm not convinced of the need for > this browser-object-class switching, because the browser-object system > is built on a semantics of prefix commands. However, I'm willing to > suspend judgement and see where this line of development leads.
I like the idea of integrating the completion and browser object systems; I think it will be both more flexible and simpler to understand. Also, as browser object classes are selected by prefix commands it will be natural to think of completion types in the same way, so I may not miss changing them on the fly. On the other hand I sometimes find when I've typed a command that I want to then change the object class. I currently quit the command, change the class and redo the command. So maybe changing object classes after having typed the command is a worthwhile addition. For the particular case of "narrowing" I have an alternative suggestion. If the list is long enough to require this, then perhaps a little pop up list isn't the best presentation. There could be a key to "promote" the completion list to become a new fully-fledged buffer containing the list. This can be navigated like a conventional buffer, but there could also be special commands to limit the items seen. This has an analogue in the Gnus "limit" (/) facility. regards, David. IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
