From: Eli Zaretskii <eliz@gnu.org>
To: rudalics@gmx.at
Cc: john@yates-sheets.org, emacs-devel@gnu.org
Subject: Re: Emphasizing the top of the frame
Date: Wed, 26 Oct 2016 21:51:57 +0300 [thread overview]
Message-ID: <83r373t036.fsf@gnu.org> (raw)
In-Reply-To: <83shrjt0lt.fsf@gnu.org> (message from Eli Zaretskii on Wed, 26 Oct 2016 21:40:46 +0300)
> Date: Wed, 26 Oct 2016 21:40:46 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org, john@yates-sheets.org
>
> > Date: Wed, 26 Oct 2016 19:56:07 +0200
> > From: martin rudalics <rudalics@gmx.at>
> > CC: john@yates-sheets.org, emacs-devel@gnu.org
> >
> > >> But for that it (1) has to "walk the window tree as well" and (2) know
> > >> where to draw the minibuffer window.
> > >
> > > No, it doesn't. The window glyph matrices on TTY frames are actually
> > > portions of the frame glyph matrix, so whenever a window's glyphs are
> > > updated by xdisp.c, the corresponding glyphs of the frame are
> > > automagically updated as well.
> >
> > Looks like changing the minibuffer position is harder for TTY frames.
>
> I'm not sure.
Btw, I'm not sure this is even desirable for TTY frames. Does anyone
really run huge xterm windows on such large displays?
next prev parent reply other threads:[~2016-10-26 18:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 17:53 Emphasizing the top of the frame John Yates
2016-10-25 18:04 ` Clément Pit--Claudel
2016-10-25 18:06 ` Drew Adams
2016-10-25 18:27 ` Eli Zaretskii
2016-10-25 18:40 ` Eli Zaretskii
2016-10-26 8:10 ` martin rudalics
2016-10-26 12:00 ` Eli Zaretskii
2016-10-26 12:31 ` martin rudalics
2016-10-26 13:13 ` Eli Zaretskii
2016-10-26 14:23 ` martin rudalics
2016-10-26 14:58 ` Eli Zaretskii
2016-10-26 17:56 ` martin rudalics
2016-10-26 18:40 ` Eli Zaretskii
2016-10-26 18:51 ` Eli Zaretskii [this message]
2016-10-26 19:26 ` Paul Eggert
2016-10-26 20:18 ` Stefan Monnier
2016-10-27 17:35 ` martin rudalics
2022-04-08 1:48 ` John Yates
2022-04-08 15:11 ` martin rudalics
2022-04-09 14:47 ` John Yates
2022-04-10 8:42 ` martin rudalics
2022-04-10 14:50 ` John Yates
2022-04-11 7:13 ` martin rudalics
2022-04-10 16:23 ` [External] : " Drew Adams
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=83r373t036.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.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).