From: Heime <heimeborgia@protonmail.com>
To: Bruno Barbier <brubar.cs@gmail.com>
Cc: Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Passing user selection to a command
Date: Tue, 19 Mar 2024 16:26:24 +0000 [thread overview]
Message-ID: <aPWd1Tq63u8aOhBuXYvcesiJvBUeYTX7n2kXMTcryOXMZegv9U4iQgl307Yx8hmQkawfFSrVFBQaTB7CI-GhJX12y8-8BV8TRluOqevf8Ys=@protonmail.com> (raw)
In-Reply-To: <65f9b599.df0a0220.dd35a.fd59@mx.google.com>
On Wednesday, March 20th, 2024 at 3:56 AM, Bruno Barbier <brubar.cs@gmail.com> wrote:
> Heime heimeborgia@protonmail.com writes:
>
> > The documentation for activate-input-method says
> >
> > "If some other input method is already active, turn it off first."
> >
> > It is not very clear whether the user should turn it off, or whether the
> > activate-input-method function will turn INPUT-METHOD off automatically.
>
>
> I'm not a native speaker; I agree it could be both. I've even checked
> the source code before answering to be sure ;-)
Changing the documentation to clarify the behavior of activate-input-method
would indeed be beneficial for users. If the documentation clearly explains
whether activate-input-method turns off the current input method automatically
before activating the new one, or if users need to explicitly deactivate it
with set-input-method, they can make informed decisions.
Correct Usage: Clear documentation hel
next prev parent reply other threads:[~2024-03-19 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 10:01 Passing user selection to a command Heime
2024-03-19 11:01 ` Bruno Barbier
2024-03-19 12:21 ` Heime
2024-03-19 12:32 ` Bruno Barbier
2024-03-19 14:19 ` Heime
2024-03-19 15:56 ` Bruno Barbier
2024-03-19 16:26 ` Heime [this message]
2024-03-19 16:11 ` Stefan Monnier via Users list for the GNU Emacs text editor
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='aPWd1Tq63u8aOhBuXYvcesiJvBUeYTX7n2kXMTcryOXMZegv9U4iQgl307Yx8hmQkawfFSrVFBQaTB7CI-GhJX12y8-8BV8TRluOqevf8Ys=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=brubar.cs@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).