[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#16691: 24.3.50; emacs_backtrace.txt
From: |
Eli Zaretskii |
Subject: |
bug#16691: 24.3.50; emacs_backtrace.txt |
Date: |
Sun, 09 Feb 2014 22:20:19 +0200 |
> 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.
- bug#16691: 24.3.50; emacs_backtrace.txt, (continued)
- bug#16691: 24.3.50; emacs_backtrace.txt, Juanma Barranquero, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, martin rudalics, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, Glenn Morris, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, Glenn Morris, 2014/02/08
- bug#16691: 24.3.50; emacs_backtrace.txt, martin rudalics, 2014/02/09
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/09
- bug#16691: 24.3.50; emacs_backtrace.txt, martin rudalics, 2014/02/09
- bug#16691: 24.3.50; emacs_backtrace.txt,
Eli Zaretskii <=
- bug#16691: 24.3.50; emacs_backtrace.txt, martin rudalics, 2014/02/10
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/10
- bug#16691: 24.3.50; emacs_backtrace.txt, martin rudalics, 2014/02/10
- bug#16691: 24.3.50; emacs_backtrace.txt, Eli Zaretskii, 2014/02/10