From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to recognize keyboard insertion? Date: Sat, 31 Oct 2009 23:23:07 +0200 Message-ID: <83ljircl6s.fsf@gnu.org> References: <83vdhvd096.fsf@gnu.org> <4AEC6CC5.3010009@harpegolden.net> <83skczcwes.fsf@gnu.org> <4AEC75C3.900@harpegolden.net> <83r5sjctup.fsf@gnu.org> <4AEC8F4A.8070205@harpegolden.net> <83my37coyw.fsf@gnu.org> <4AECA148.4090809@harpegolden.net> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1257024252 1688 80.91.229.12 (31 Oct 2009 21:24:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 31 Oct 2009 21:24:12 +0000 (UTC) Cc: emacs-devel@gnu.org To: David De La Harpe Golden Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 31 22:24:04 2009 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 1N4LQY-0005qk-8t for ged-emacs-devel@m.gmane.org; Sat, 31 Oct 2009 22:24:02 +0100 Original-Received: from localhost ([127.0.0.1]:47188 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N4LQX-0005CO-DE for ged-emacs-devel@m.gmane.org; Sat, 31 Oct 2009 17:24:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N4LQK-00059Q-PV for emacs-devel@gnu.org; Sat, 31 Oct 2009 17:23:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N4LQG-00057h-Td for emacs-devel@gnu.org; Sat, 31 Oct 2009 17:23:48 -0400 Original-Received: from [199.232.76.173] (port=51456 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N4LQG-00057b-Mq for emacs-devel@gnu.org; Sat, 31 Oct 2009 17:23:44 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:59802) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N4LQG-0008PY-AE for emacs-devel@gnu.org; Sat, 31 Oct 2009 17:23:44 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0KSE00500BX0EP00@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Sat, 31 Oct 2009 23:23:08 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.70.37.193]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KSE003B6E2I93A0@a-mtaout22.012.net.il>; Sat, 31 Oct 2009 23:23:07 +0200 (IST) In-reply-to: <4AECA148.4090809@harpegolden.net> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (beta) 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:116534 Archived-At: > Date: Sat, 31 Oct 2009 20:42:48 +0000 > From: David De La Harpe Golden > CC: emacs-devel@gnu.org > > Maybe one way to handle it would be to make an (emacs level) input > method autoswitcher, that swaps emacs input methods as the rtl/ltr > context switches with point movement. i.e. allow (but don't require) > rtl and ltr contexts to have different emacs input methods. We can have input methods switched on and off depending on surrounding characters, but how will this solve the problem that different methods of inputting the same character behave differently with mirrored characters? A user can conceptually type a character either via an Emacs input method or via the OS keyboard, in the same place, can't she? > Then there could be variant emacs input methods with various > transpositions suitable for use with various os-level keymaps. Are you saying that Emacs should have a way of knowing which OS-level keyboard layout (or keyboard language, in Windows parlance) was used to insert the character? If so, how to do that? Or are you saying that switching on a suitable input method, depending on surrounding characters, will eliminate the need to know how the character was inserted? If so, please explain why you think so, because I don't follow. > And you don't have to be able to _record_ whether an inserted > character came from the keyboard. I don't need to record that, I just need to know that when the character is inserted. After it's inserted, this information is not needed anymore, because display-time mirroring has enough information to DTRT.