From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: larsi@gnus.org, 51473@debbugs.gnu.org
Subject: bug#51473: [PATCH] Enable xwidget scrolling optimizations, and other xwidgets improvements
Date: Sun, 07 Nov 2021 14:33:21 +0200 [thread overview]
Message-ID: <83y26087se.fsf@gnu.org> (raw)
In-Reply-To: <87y260tbpj.fsf@yahoo.com> (message from Po Lu on Sun, 07 Nov 2021 20:03:04 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: larsi@gnus.org, 51473@debbugs.gnu.org
> Date: Sun, 07 Nov 2021 20:03:04 +0800
>
> > The printed representation of xwidget objects should be documented in
> > the ELisp manual, under the "Editing Types" section. In fact, we lack
> > a subsection there for xwidgets; it should be added.
> >
> > Thanks.
>
> Will this work?
With some minor changes, yes.
> +@node Xwidget Type
> +@subsection Xwidget Type
It is generally a good idea to have a @cindex entry with the name of
the section (but with lower-case letters), so that the section could
be easily found via Info-index.
> + Each window such an
> +xwidget is be displayed in
This style is better avoided: it produces long sentences that are hard
to grasp for non-native speakers, because the important part ("in") is
at the end. It is better to say it simply:
Each window that displays an xwidget will also have a @dfn{xwidget
view}, ...
And add a @cindex for "xwidget-view", again generally a good practice
of indexing each place that introduces new terminology (indicated by
@dfn).
> , which on
> +X-Windows corresponds to a single X window used to display the widget.
What about NS? And what about Wayland?
> +Neither of these objects are readable; their print syntaxes look like
> +@samp{#<xwidget>} and @samp{#<xwidget-view>}, respectively. Lisp
> +programmers should not be interested in the functionality of xwidget
> +views.
I'd drop the second of these sentences. It doesn't add anything to
the description.
Thanks.
next prev parent reply other threads:[~2021-11-07 12:33 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87zgqslafe.fsf.ref@yahoo.com>
2021-10-29 4:30 ` bug#51473: [PATCH] Enable xwidget scrolling optimizations, and other xwidgets improvements Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-29 13:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-04 23:11 ` Lars Ingebrigtsen
2021-11-05 7:20 ` Eli Zaretskii
2021-11-05 7:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 7:33 ` Lars Ingebrigtsen
2021-11-05 7:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:35 ` Lars Ingebrigtsen
2021-11-05 7:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:32 ` Lars Ingebrigtsen
2021-11-05 13:28 ` Lars Ingebrigtsen
2021-11-05 13:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-05 13:48 ` Lars Ingebrigtsen
2021-11-06 0:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 0:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 0:25 ` Lars Ingebrigtsen
2021-11-06 2:06 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 5:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 8:58 ` Eli Zaretskii
2021-11-06 10:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-06 17:42 ` Lars Ingebrigtsen
2021-11-07 0:41 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 0:55 ` Lars Ingebrigtsen
2021-11-07 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:04 ` Lars Ingebrigtsen
2021-11-07 1:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:23 ` Lars Ingebrigtsen
2021-11-07 1:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:29 ` Lars Ingebrigtsen
2021-11-07 1:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 1:39 ` Lars Ingebrigtsen
2021-11-07 1:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 2:04 ` Lars Ingebrigtsen
2021-11-07 10:09 ` Eli Zaretskii
2021-11-07 12:03 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 12:33 ` Eli Zaretskii [this message]
2021-11-07 12:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-07 12:52 ` Eli Zaretskii
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=83y26087se.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51473@debbugs.gnu.org \
--cc=larsi@gnus.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 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.