From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?B?4KS44KSu4KWA4KSwIOCkuOCkv+CkguCkuSBTYW1lZXIgU2luZ2g=?= Newsgroups: gmane.emacs.devel Subject: Re: itrans input methods and motion keys Date: Wed, 29 Jun 2022 00:14:36 +0530 Message-ID: References: <87k091dqhl.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000049de6405e2866ee2" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13464"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Visuwesh Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jun 28 20:48:06 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o6GFp-0003Lx-EG for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Jun 2022 20:48:05 +0200 Original-Received: from localhost ([::1]:54554 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o6GFo-0000d1-Ej for ged-emacs-devel@m.gmane-mx.org; Tue, 28 Jun 2022 14:48:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39742) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o6GCg-0006RG-Fl for emacs-devel@gnu.org; Tue, 28 Jun 2022 14:44:50 -0400 Original-Received: from mail-qv1-xf35.google.com ([2607:f8b0:4864:20::f35]:34404) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o6GCe-0003TL-R1 for emacs-devel@gnu.org; Tue, 28 Jun 2022 14:44:50 -0400 Original-Received: by mail-qv1-xf35.google.com with SMTP id t16so21436946qvh.1 for ; Tue, 28 Jun 2022 11:44:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QQeRZfvI98ziElinav7xFvv+pwxj4cVtdDyfGE4YWcc=; b=V5fakVm72gAR5N1l3tQHwn7a8R0x0T4kdtpLm7UHtNT77CKVaSghJNc8zKvVu1IWwB k3tfDfodplSX2c92LKIeaEpw3rn4xxZt028RfRyheDzEJAt8kBR89lTo5KxCCAA5AOBw 3Kg0FlpjRwrkK9jmkdH0r6Rir6JpfmKF8BWDK68n5IdvV/pJD+RAfrFuhH7Iaff1lm0+ vVtX7x8RNLBKqxerCrk0271ezGEZ0W7CQunzxCRU0/PpIyfMriv9MX+LMtNd/uH9IToj AeicPkhHzB27C2u/9GzNDMBQXMv3k20DIvjELTJE+aEJh9T/HeXjANio+b7nJLDSGYSI 4Mmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=QQeRZfvI98ziElinav7xFvv+pwxj4cVtdDyfGE4YWcc=; b=uoerB30Cw2dxa7M3Ro9OZ/ndJF1wGlHdvy/o8rjvp8NWiKJObKFaGhtKH3PZ3Zrsm+ NLg20e1XrW+a1k0Wj03eBxT2f+2gCafba0FrhxL1XsEE9PSDrV/njS5mP7p8mUSEIse0 nQIgIZzY3uzjViVLocc6Yog6zrnlNxyY+4dgejyhXxCYzICwTd9rspc0kZiD+az/uyhY ziuoGX8pb6cHj8IXCPqLH9JcEO6P7jcMUpv5K6taDw3OSE67ZQtbU0yur+/OwMuQ/p6s MFRYJPjQCjejt/WBWL3FaiYW0PjOtJCPKwo5kmCk5PDE7ibLjSxIAZE9kg66PhfG8FKD 0IMw== X-Gm-Message-State: AJIora/BMXvrTE3NwoD6i+AQ1cobO50DxBQjrKPpn/9kFOqD4IFa7t/c eFXMwiokspDJCsFLlg61ZpOzxHiXmAeaTSbhW2c= X-Google-Smtp-Source: AGRyM1tGeLwHvhrTtEMxWAyHZQz2IjMgSZbuq6N2uMpDzSYcFbKfem8oDbhVIEcN1EOnr9YG7ITDc2cX9eG2cB3El9Q= X-Received: by 2002:a0c:fc43:0:b0:470:41de:2bbd with SMTP id w3-20020a0cfc43000000b0047041de2bbdmr4920091qvp.79.1656441887381; Tue, 28 Jun 2022 11:44:47 -0700 (PDT) In-Reply-To: <87k091dqhl.fsf@gmail.com> Received-SPF: pass client-ip=2607:f8b0:4864:20::f35; envelope-from=lumarzeli30@gmail.com; helo=mail-qv1-xf35.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:291696 Archived-At: --00000000000049de6405e2866ee2 Content-Type: text/plain; charset="UTF-8" I am sorry I do not use the itrans input methods, therefore do not know much about it :( So may I know why are motion keys disabled while typing in these input methods? Thanks. On Tue, Jun 28, 2022 at 4:06 PM Visuwesh wrote: > Dear all, > > I'm posting this in emacs-devel instead of filing a bug report since I > want this to get a bit more attraction. I'm also CCing Sameer Singh in > hopes that he can give insight into the non-Tamil side of things. > > Currently, the itrans input methods are defined using the function > quail-define-indian-trans-package in lisp/leim/quail/indian.el. This > function calls quail-define-package with a nil SIMPLE argument which > steals the commonly used motion keys C-f, C-b, C-n, C-p. AFAICT from > what I read in quail a year or so ago, this argument is more useful for > the Chinese and the Japanese input methods but not so much for simple > IMs like the itrans one which only does transliteration. Besides, even > if an IM has one to many translation i.e., if "a" can be translated to > "a->" and "a->>", and the SIMPLE argument is non-nil, one can use the > number keys to select the alternate translation. > > Since the nil value of SIMPLE argument gives no real benefit in the case > of tamil-itrans IM, I would like to change it to t so that we can get > the motion keys back. However, I have only ever used the Tamil IM and > thus have no idea about the other languages. Then we can adjust the > quail-define-indian-trans-package function to pass a custom SIMPLE > argument instead. > --00000000000049de6405e2866ee2 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I am sorry I do not use the itrans input methods, the= refore do not know much about it :(
So may I know why are motion = keys disabled while typing in these input methods?

Thanks.

On Tue, Jun 28, 2022 at 4:06 PM Visuwesh <visuweshm@gmail.com> wrote:
Dear all,

I'm posting this in emacs-devel instead of filing a bug report since I<= br> want this to get a bit more attraction.=C2=A0 I'm also CCing Sameer Sin= gh in
hopes that he can give insight into the non-Tamil side of things.

Currently, the itrans input methods are defined using the function
quail-define-indian-trans-package in lisp/leim/quail/indian.el.=C2=A0 This<= br> function calls quail-define-package with a nil SIMPLE argument which
steals the commonly used motion keys C-f, C-b, C-n, C-p.=C2=A0 AFAICT from<= br> what I read in quail a year or so ago, this argument is more useful for
the Chinese and the Japanese input methods but not so much for simple
IMs like the itrans one which only does transliteration.=C2=A0 Besides, eve= n
if an IM has one to many translation i.e., if "a" can be translat= ed to
"a->" and "a->>", and the SIMPLE argument is n= on-nil, one can use the
number keys to select the alternate translation.

Since the nil value of SIMPLE argument gives no real benefit in the case of tamil-itrans IM, I would like to change it to t so that we can get
the motion keys back.=C2=A0 However, I have only ever used the Tamil IM and=
thus have no idea about the other languages.=C2=A0 Then we can adjust the quail-define-indian-trans-package function to pass a custom SIMPLE
argument instead.
--00000000000049de6405e2866ee2--