From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Function for deleting a key binding in a sparse keymap Date: Sun, 11 Dec 2005 00:45:16 +0100 Message-ID: <439B688C.1090207@student.lu.se> References: <3cc04a73cc1b1a.3cc1b1a3cc04a7@net.lu.se> <43987D21.4070200@student.lu.se> <4398C8F2.8060301@student.lu.se> <4399E538.2080909@student.lu.se> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------030908030202080105020808" X-Trace: sea.gmane.org 1134258342 9188 80.91.229.2 (10 Dec 2005 23:45:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 10 Dec 2005 23:45:42 +0000 (UTC) Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, storm@cua.dk Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 11 00:45:35 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ElEPG-000702-5W for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2005 00:45:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElEPf-0003A5-Gd for ged-emacs-devel@m.gmane.org; Sat, 10 Dec 2005 18:45:59 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ElEPT-00037W-4D for emacs-devel@gnu.org; Sat, 10 Dec 2005 18:45:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ElEPS-00036m-5H for emacs-devel@gnu.org; Sat, 10 Dec 2005 18:45:46 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElEPR-00036e-VO for emacs-devel@gnu.org; Sat, 10 Dec 2005 18:45:46 -0500 Original-Received: from [81.228.11.98] (helo=pne-smtpout1-sn1.fre.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1ElEQs-000528-Ok; Sat, 10 Dec 2005 18:47:15 -0500 Original-Received: from [192.168.123.121] (83.249.218.244) by pne-smtpout1-sn1.fre.skanova.net (7.2.060.1) id 4396EEA4000F810A; Sun, 11 Dec 2005 00:45:17 +0100 User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en Original-To: rms@gnu.org In-Reply-To: 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:47412 Archived-At: This is a multi-part message in MIME format. --------------030908030202080105020808 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Richard M. Stallman wrote: > Go through the list below step by step. As soon as a hit is found in > any keymap (see KeyLookup) you normally are ready. > >Saying "you" is a peculiar way to word it--it is Enacs that does these >things. Could you rewrite this in terms of what Emacs does? > >Also, could you (or someone) turn it into Texinfo? > > I have attached a new version. This is in Texinfo format and written to be placed at the bottom of @node Active Keymaps in keymaps.texi. *** Some questions: - Could someone please tell what is happening when key lookup finds a keymap entry? If no hit is found in the new keymap which keymap is then the next? - Maybe the node should have an entry in the index? - I do not understand why @emph{TERM} gives a result looking like _TERM_ after running "make info". It is instead converted to underlined blue text when I test with texinfo-format-region. (This is on w32. A difference might be that texinfo-format-region is using Cygwins makeinfo and "make info" is using makeinfo from GnuWin32. Both are version 4.8.) - How is fill supposed to work? It seems like the texinfo makeup is not excluded so to say when doing a fill-paragraph. Or am I mistaken? --------------030908030202080105020808 Content-Type: text/plain; name="finding-keymap.texi" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="finding-keymap.texi" @subsection Finding the keymap to use The list below describes step by step how Emacs finds a keymap from a given key sequence. As soon as a hit is found in any keymap (see @ref{Key Lookup}) then if the keymap entry is a function the search is over. However if the keymap entry is a variable symbol or a string then Emacs restarts with the variable symbol value or the string from FIRST-MAP. The keymap entry could also be a keymap. In that case the next event is looked up in that keymap. (But what happens if there is no hit there, I can not find any documentation on this???) @noindent @emph{Note 1:} When Emacs finally find a function symbol through this process it also checks for command remapping. This just replaces the function symbol with another. It is not recursive. @noindent @emph{Note 2:} You may find the function @code{current-active-maps} useful when looking into this. @table @asis @item START-HERE: First apply @code{extra-keyboard-modifiers} mask to each keyboard character read. @end table @itemize @bullet @item Each character read from the keyboard may be translated according to @code{keyboard-translate-table}. @item Characters that are self-inserting are translated according to @code{translation-table-for-input}. If a character is self-inserting then stop here. @item Translate meta characters according to @code{meta-prefix-char} to a two character sequence. @end itemize @table @asis @item FIRST-MAP: Look in @code{special-event-map}. @end table @itemize @bullet @item If using @code{read-from-minibuffer} (directly or indirectly) then look in the keymap given as parameter then look in this. Otherwise look in @code{minibuffer-local-map}. @item If using @code{read-no-blanks-input} to read from minibuffer then look in @code{minibuffer-local-ns-map} first and then @code{minibuffer-local-map}. @item If overriding-terminal-local-map look in this. Then go to GLOBAL. @item If overriding-local-map look in this. Then go to GLOBAL. @item Is there a "keymap" property of the text or overlay at point? @item Look for minor mode keymaps in @code{emulation-mode-map-alists}. @item Look for minor mode keymaps in @code{minor-mode-overriding-map-alist} @item Look for minor mode keymaps in @code{minor-mode-map-alist}. @item Is there a @code{local-map} property of the text or overlay at point? @item Is there a "local keymap" (those are for major modes)? @end itemize @table @asis @item GLOBAL: Look in the "current global keymap". (This is returned by @code{current-global-map} and may be different from @code{global-map}, see @code{use-global-map}.) @end table @itemize @bullet @item If it is an ASCII function key sequences then look in @code{function-key-map}. This map transforms to Emacs key sequences. @item The possibly transformed sequence after applying @code{function-key-map} is now handled to @code{key-translation-map} which works the same way. @item If any transformation was made by @code{function-key-map} or @code{key-translation-map} then take the new sequence and go back to FIRST-MAP. @end itemize --------------030908030202080105020808 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel --------------030908030202080105020808--