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: Mon, 10 Feb 2014 20:44:06 +0200 [thread overview]
Message-ID: <83mwhyu7t5.fsf@gnu.org> (raw)
In-Reply-To: <52F91BED.2080108@gmx.at>
> Date: Mon, 10 Feb 2014 19:35:25 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: lekktu@gmail.com, drew.adams@oracle.com, 16691@debbugs.gnu.org
>
> > If you meant row->y, then it is used in many different places,
> > including the display back-end,
>
> Where is the display back-end? If it's update_window
It is _called_ by update_window. In update_text_area, you will see
the calls to rif->write_glyphs, which eventually calls the back-end
(xterm.c, w32term.c, term.c, etc.).
> we there set
>
> yb = window_text_bottom_y (w);
>
> and then
>
> mode_line_row->y = yb;
>
> so any prior notion of that row's y is lost. And for the header line we
> do
>
> header_line_row->y = 0;
>
> But this still doesn't use row->y. Where is the backend that uses
> row->y to determine where on the screen to draw that row?
Are you talking only about the mode line and the header line? If so,
then yes, those rows don't need the y coordinate, as they "know" where
it is in advance.
I thought you were asking a more general question about row->x and
row->y.
next prev parent reply other threads:[~2014-02-10 18:44 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
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 [this message]
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=83mwhyu7t5.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).