From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: inputting characters by hexadigit Date: Wed, 23 Jul 2008 15:19:02 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <86tzegcq15.fsf@lifelogs.com> References: <868ww3vydn.fsf@lifelogs.com> <87myki6fqp.fsf@jurta.org> <87mykhz6tf.fsf@jurta.org> <87tzeokrku.fsf@jurta.org> <87od4wgg8p.fsf@catnip.gol.com> <86od4vmi5i.fsf@lifelogs.com> <873am6n21q.fsf@jurta.org> <87sku5if8t.fsf_-_@jurta.org> <87od4sti4g.fsf@jurta.org> <867ibcekf3.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1216844115 3999 80.91.229.12 (23 Jul 2008 20:15:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 23 Jul 2008 20:15:15 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 23 22:16:04 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KLkkj-0004lk-AN for ged-emacs-devel@m.gmane.org; Wed, 23 Jul 2008 22:16:02 +0200 Original-Received: from localhost ([127.0.0.1]:60296 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KLkjp-0001CP-8i for ged-emacs-devel@m.gmane.org; Wed, 23 Jul 2008 16:15:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KLkjQ-0000z9-EG for emacs-devel@gnu.org; Wed, 23 Jul 2008 16:14:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KLkjP-0000ye-Ti for emacs-devel@gnu.org; Wed, 23 Jul 2008 16:14:40 -0400 Original-Received: from [199.232.76.173] (port=41848 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KLkjP-0000yS-Hv for emacs-devel@gnu.org; Wed, 23 Jul 2008 16:14:39 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:36269 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KLkjP-0000F2-2M for emacs-devel@gnu.org; Wed, 23 Jul 2008 16:14:39 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1KLkjM-0001Rf-Fr for emacs-devel@gnu.org; Wed, 23 Jul 2008 20:14:36 +0000 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jul 2008 20:14:36 +0000 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jul 2008 20:14:36 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 52 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:iwzRwkUhC3LCklMRMPzGCZKVg3M= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:101333 Archived-At: On Wed, 23 Jul 2008 15:31:36 -0400 Stefan Monnier wrote: >> Can completions be cascaded somehow? The first tier would show all the >> common first words, e.g. ... AEGEAN APL GREEK ... and then selecting >> something from the first tier would cascade down to the second tier. SM> The slow display should only happen when the list is really long, SM> i.e. basically if you hit TAB with an empty minibuffer. So we could SM> indeed easily use a different completion behavior in this case. >> This might actually be a sensible suggestion for any completion list >> with more than 100 or so members, and the tier separation can be done >> with the word syntax of the current mode. SM> You mean show the list as a tree? That cannot be done with the current SM> default completio code. But some variant of it can be done. E.g. we SM> can use a completion similar to file names, so additionally to SM> we could accept input of the form / and SM> provide completion on this (and if the completion list on is too SM> long, don't display it: only display the completion on SM> /). To clarify my proposal: Split on the word syntax, so (taking the Unicode example) hitting TAB initially gives APL (200 candidates) AEGEAN (20 candidates) GREEK (50 candidtates) then as the user types A, the list becomes APL (200 candidates) AEGEAN (20 candidates) with the A highlighted, and so on. As soon as less than X candidates are available the usual list is displayed; X is customizable but 40 by default. The word syntax can depend on the current mode, or be overridden by the function being called. The advantage over categories, which you suggested, is that the completion code won't need categories supplied--it automatically gets them based on the word syntax, so it's less work for the programmer and thus more likely to get used everywhere and be suitable as a drop-in replacement for the current completion code. The current behavior (e.g. M-x TAB) is nearly unusable without either apropos or icicles (that I know of) to search through the list. Ted