From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Cc: Po Lu <luangruo@yahoo.com>
Subject: Re: master f041d61008 2/3: Improve documentation of the preedit-text event
Date: Fri, 07 Jan 2022 10:49:44 +0100 [thread overview]
Message-ID: <87a6g77u4n.fsf@gmail.com> (raw)
In-Reply-To: <20220107092636.08509C0DA1D@vcs2.savannah.gnu.org> (Po Lu via Mailing list for Emacs changes's message of "Fri, 7 Jan 2022 04:26:35 -0500 (EST)")
>>>>> On Fri, 7 Jan 2022 04:26:35 -0500 (EST), Po Lu via Mailing list for Emacs changes <emacs-diffs@gnu.org> said:
Po> branch: master
Po> commit f041d610083ca0815ab18c589f115bacc523b9bb
Po> Author: Po Lu <luangruo@yahoo.com>
Po> Commit: Po Lu <luangruo@yahoo.com>
Po> Improve documentation of the preedit-text event
Po> * doc/lispref/commands.texi (Misc Events): Document how
Po> `preedit-text' events are used.
Po> ---
Po> doc/lispref/commands.texi | 4 +++-
Po> 1 file changed, 3 insertions(+), 1 deletion(-)
Po> diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
Po> index eb364d2f49..062b8ea911 100644
Po> --- a/doc/lispref/commands.texi
Po> +++ b/doc/lispref/commands.texi
Po> @@ -2140,7 +2140,9 @@ cursor. It can be @code{nil}, which means to remove any text
Po> previously displayed. @c FIXME: what is the value of ARG on PGTK?
Po> This is a special event (@pxref{Special Events}), which normally
Po> -should not be bound by the user to any command.
Po> +should not be bound by the user to any command. Emacs will typically
Po> +the text contained in the event behind the cursor on-screen when it is
Po> +received.
I think youʼre missing a verb. And what does "behind the cursor
on-screen" mean? An overlay? (plus I thought this was disabled by
default now?)
Robert
--
next parent reply other threads:[~2022-01-07 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164154759534.24569.1062687039370550695@vcs2.savannah.gnu.org>
[not found] ` <20220107092636.08509C0DA1D@vcs2.savannah.gnu.org>
2022-01-07 9:49 ` Robert Pluim [this message]
2022-01-07 10:48 ` master f041d61008 2/3: Improve documentation of the preedit-text event Po Lu
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=87a6g77u4n.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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 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).