From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 16691@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#16691: 24.3.50; emacs_backtrace.txt
Date: Sun, 09 Feb 2014 22:20:19 +0200 [thread overview]
Message-ID: <83fvnsujgc.fsf@gnu.org> (raw)
In-Reply-To: <52F7CFC4.2030905@gmx.at>
> Date: Sun, 09 Feb 2014 19:58:12 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: lekktu@gmail.com, drew.adams@oracle.com, 16691@debbugs.gnu.org
>
> - short used[1 + LAST_AREA]: What does "Number of glyphs actually filled
> in areas." mean? Does this mean that for example the first element is
> zero when the left margin doesn't exist?
Not necessarily: the margin could exist, but be empty. And note that
in frame glyph matrices (used on a TTY), there's only one area: the
TEXT_AREA; the marginal areas don't have their glyphs[] arrays
allocated.
> - int x, y: Where and how are these set for a particular row (including
> header- and mode-line) and when and how are these eventually consumed?
> This is the greatest mystery for me so far.
They are assigned in display_line and display_string. Examples from
display_line:
row->y = it->current_y;
[...]
if (it->current_x - it->pixel_width < it->first_visible_x)
row->x = x - it->first_visible_x;
Mode line and header line are generated from strings, so look in
display_mode_line and display_string.
Not sure what you mean by "consumed". Consumed by whom and for what
purposes?
> - int visible_height: "Partially visible rows may be found at the top
> and bottom of a window." Is it true that we can draw partially
> visible rows at the top of the window?
I think this is only possible when a single row is too large to fit a
window.
next prev parent reply other threads:[~2014-02-09 20:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 17:30 bug#16691: 24.3.50; emacs_backtrace.txt Drew Adams
2014-02-08 19:22 ` Juanma Barranquero
2014-02-08 19:34 ` Eli Zaretskii
2014-02-08 20:06 ` martin rudalics
2014-02-08 20:31 ` Eli Zaretskii
2014-02-08 20:40 ` Glenn Morris
2014-02-08 20:55 ` Eli Zaretskii
2014-02-08 23:25 ` Glenn Morris
2014-02-09 11:04 ` martin rudalics
2014-02-09 16:30 ` Eli Zaretskii
2014-02-09 18:58 ` martin rudalics
2014-02-09 20:20 ` Eli Zaretskii [this message]
2014-02-10 8:14 ` martin rudalics
2014-02-10 17:42 ` Eli Zaretskii
2014-02-10 18:35 ` martin rudalics
2014-02-10 18:44 ` Eli Zaretskii
2015-12-26 13:26 ` Lars Ingebrigtsen
2015-12-26 13:38 ` 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
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=83fvnsujgc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16691@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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).