From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: mouse-autoselect-window-select
Date: Wed, 14 Aug 2013 21:00:22 +0300 [thread overview]
Message-ID: <838v04p2yx.fsf@gnu.org> (raw)
In-Reply-To: <520BB93C.2070303@gmx.at>
> Date: Wed, 14 Aug 2013 19:07:08 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> > You could exclude the case of fringes-outside-margins. No need to
> > wait for a complaint to DTRT.
>
> What is TRT? According to what you say here the following text from the
> Elisp manual which informally mentions the "text area" of a window
>
> The "body height" of a window is the height of its text area, which
> does not include the mode or header line. Similarly, the "body width"
> is the width of the text area, which does not include the scroll bar,
> fringes, or margins.
>
> is incorrect.
That's "text area" overloaded for you. From the technical POV of the
display engine, text area indeed does not include the display
margins. But from the user's POV, I think it surely does, because it
displays the same objects as the text area does: text and images, and
that display is created the same way as you'd display an overlay or
display string in the "text area".
next prev parent reply other threads:[~2013-08-14 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 15:21 mouse-autoselect-window-select Eli Zaretskii
2013-08-14 15:36 ` mouse-autoselect-window-select martin rudalics
2013-08-14 15:59 ` mouse-autoselect-window-select Eli Zaretskii
2013-08-14 17:07 ` mouse-autoselect-window-select martin rudalics
2013-08-14 18:00 ` Eli Zaretskii [this message]
2013-08-15 10:20 ` mouse-autoselect-window-select martin rudalics
2013-08-15 14:59 ` mouse-autoselect-window-select Eli Zaretskii
2013-08-16 10:03 ` mouse-autoselect-window-select martin rudalics
2013-08-16 10:28 ` mouse-autoselect-window-select Eli Zaretskii
2013-08-15 15:45 ` mouse-autoselect-window-select Davis Herring
2013-08-16 10:03 ` mouse-autoselect-window-select martin rudalics
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=838v04p2yx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).