From: Ali AlipourR <alipoor90@gmail.com>
To: 66325@debbugs.gnu.org
Subject: bug#66325: `inherit-input-method`'s poor behavior
Date: Tue, 3 Oct 2023 19:55:42 +0330 [thread overview]
Message-ID: <CABvhJLig9saigDoBz9FX=rs72y3XDb1O4s=8JcHbD8KsEEwXRA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
When you open a minibuffer with a non-nil inherit-input-method argument,
the minibuffer will inherit its -default- input method from the parent
buffer. This much is fine and desirable behavior.
However, with this option enabled, you can no longer change your input
method while editing inside the minibuffer. (i.e. using C-\ or
toggle-input-method)
This is poor behavior, since if you are someone who uses input methods
(i.e. uses emacs to write in languages other than English) you often want
to use multiple input methods while editing inside a minibuffer.
For example, to enter a mixed English-Chinese/Arabic/Persian/... text as a
search term etc.
Acceptable behavior would be if even with inherit-input-method enabled,
Emacs allowed changing the input method inside the minibuffer (And just
default to the input-method that it inherited from the parent buffer).
Optimal behavior would be if change of input-method inside a minibuffer
also changed the current input method of the parent buffer, so that when
you close the minibuffer and return to parent buffer, you have your last
selected input method that you used inside the minibuffer, selected and
ready to use inside the parent buffer.
Sorry if the technical terms used aren't 100% accurate, as I'm still an
Emacs newbie ...
Thanks,
Ali
[-- Attachment #2: Type: text/html, Size: 1381 bytes --]
next reply other threads:[~2023-10-03 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 16:25 Ali AlipourR [this message]
2023-10-03 17:17 ` bug#66325: `inherit-input-method`'s poor behavior Eli Zaretskii
2024-01-10 10:35 ` Stefan Kangas
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='CABvhJLig9saigDoBz9FX=rs72y3XDb1O4s=8JcHbD8KsEEwXRA@mail.gmail.com' \
--to=alipoor90@gmail.com \
--cc=66325@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).