From: Kevin Vigouroux via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42154@debbugs.gnu.org
Subject: bug#42154: 26.3; [DOC] This wording is too complex: frame's window-system window.
Date: Thu, 02 Jul 2020 14:15:09 +0200 [thread overview]
Message-ID: <87pn9eyuya.fsf@laposte.net> (raw)
In-Reply-To: <83lfk3xjrp.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 01 Jul 2020 19:49:46 +0300")
Yes, it is more clear.
Can we replace the expression "window-system's window" by "graphical
application" if appropriate?
The former expression is a bit of jargon. See the following rewording.
On a graphical terminal we distinguish two types of frames. A normal
"top-level frame" is a usual graphical application; this Emacs frame may
be directly managed by the window system. A child frame is a kind of
special frame that depends on another frame and is handled by Emacs.
[Elisp manual, chapter 19. Frames]
On a graphical terminal we distinguish two types of frames: A normal
“top-level frame” is a frame whose window-system window is a child of
the window-system’s root window for that terminal. A child frame is a
frame whose window-system window is the child of the window-system
window of another Emacs frame. *Note Child Frames*.
next prev parent reply other threads:[~2020-07-02 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 16:21 bug#42154: 26.3; [DOC] This wording is too complex: frame's window-system window Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-01 16:49 ` Eli Zaretskii
2020-07-02 12:15 ` Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2020-07-02 13:30 ` Eli Zaretskii
2020-07-02 3:47 ` Richard Stallman
2020-07-02 13:03 ` Eli Zaretskii
2020-07-04 7:21 ` Eli Zaretskii
2020-07-05 2:35 ` Richard Stallman
2020-07-05 14:33 ` 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=87pn9eyuya.fsf@laposte.net \
--to=bug-gnu-emacs@gnu.org \
--cc=42154@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ke.vigouroux@laposte.net \
/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.