From: "André A. Gomes" <andremegafone@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Yuri Khan <yuri.v.khan@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
"Perry E. Metzger" <perry@piermont.com>,
emacs-devel <emacs-devel@gnu.org>, Juri Linkov <juri@linkov.net>
Subject: Re: not quite understanding input methods
Date: Wed, 01 Sep 2021 16:19:10 +0300 [thread overview]
Message-ID: <87bl5cfn75.fsf@gmail.com> (raw)
In-Reply-To: <CALDnm53bTQ-pN8fM=g5JCqdn9tPaZSY3ZFb1wTgEmW+yQRYn1Q@mail.gmail.com> ("João Távora"'s message of "Wed, 1 Sep 2021 13:35:59 +0100")
João Távora <joaotavora@gmail.com> writes:
> Even when they are, they don't work the same way across operating
> systems, whereas Emacs' portuguese-prefix does, perfectly predictably.
Exactly!
This is a tangent topic, but let me share my experience. I don't use
any portuguese IM for a long time. To type in any latin-based language
I use the "us altgr-intl" IM and the compose key when needed (seldom).
Of course that such a solution makes sense when one is willing to
dismiss old muscle memory (of using the pt keyboard layout), and acquire
a new habit.
Now for the crucial point. Do you go back forth the US and PT IM a lot?
In other words, how often do you type "cora;ão"?
Or do you use the "portuguese-prefix exclusively inside of Emacs?
I'm trying to gather some user-experience when it comes to my toy
project regarding input methods in Emacs. Thanks.
--
André A. Gomes
"Free Thought, Free World"
next prev parent reply other threads:[~2021-09-01 13:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 17:24 not quite understanding input methods Perry E. Metzger
2021-08-30 17:37 ` Stefan Monnier
2021-08-30 17:45 ` Perry E. Metzger
2021-08-30 18:00 ` Stefan Monnier
2021-08-30 18:22 ` Eli Zaretskii
2021-08-30 18:34 ` Perry E. Metzger
2021-08-30 18:39 ` Eli Zaretskii
2021-08-30 18:43 ` Perry E. Metzger
2021-08-30 18:37 ` Perry E. Metzger
2021-08-30 19:00 ` Perry E. Metzger
2021-08-30 19:08 ` Eli Zaretskii
2021-08-30 19:13 ` Perry E. Metzger
2021-08-30 19:19 ` Stefan Monnier
2021-08-30 19:26 ` Perry E. Metzger
2021-08-30 19:31 ` Eli Zaretskii
2021-08-30 20:12 ` Stefan Monnier
2021-08-30 19:28 ` Eli Zaretskii
2021-08-30 20:29 ` André A. Gomes
2021-09-01 5:44 ` Yuri Khan
2021-09-01 7:23 ` Juri Linkov
2021-09-01 7:43 ` Yuri Khan
2021-09-01 8:37 ` tomas
2021-09-01 9:14 ` Joost Kremers
2021-09-01 13:17 ` Perry E. Metzger
2021-09-01 12:05 ` Eli Zaretskii
2021-09-01 12:35 ` João Távora
2021-09-01 13:19 ` André A. Gomes [this message]
2021-09-01 14:05 ` João Távora
2021-09-01 13:03 ` André A. Gomes
2021-09-01 13:02 ` Perry E. Metzger
2021-09-02 12:00 ` Maxim Nikulin
2021-09-02 13:03 ` Filipp Gunbin
2021-09-01 12:58 ` Perry E. Metzger
2021-09-01 12:51 ` Perry E. Metzger
2021-09-01 13:29 ` Partially answering my own question (was Re: not quite understanding input methods) Perry E. Metzger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bl5cfn75.fsf@gmail.com \
--to=andremegafone@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=juri@linkov.net \
--cc=perry@piermont.com \
--cc=yuri.v.khan@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.