From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 14062@debbugs.gnu.org
Subject: bug#14062: 24.3.50; emacs_backtrace.txt
Date: Sat, 04 May 2013 15:33:05 +0300 [thread overview]
Message-ID: <83vc6ylybi.fsf@gnu.org> (raw)
In-Reply-To: <5184FEAB.8040301@gmx.at>
> Date: Sat, 04 May 2013 14:27:23 +0200
> From: martin rudalics <rudalics@gmx.at>
>
> > After staring at the code again, I might be able to explain to myself
> > why the BUFFERP test was not enough. I rearranged the tests in the
> > WINDOW_WANTS_HEADER_LINE_P macro so that hopefully this will not
> > happen again.
>
> I fail to understand what FRAME_WANTS_MODELINE_P is good for. I
> removed it in my code long ago.
It causes the header line to disappear when the window is too small to
show both the modeline and the header line. The limit of the window
size where that happens obviously should be different depending on
whether the window does or does not have a modeline.
next prev parent reply other threads:[~2013-05-04 12:33 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 23:33 bug#14062: 24.3.50; emacs_backtrace.txt Drew Adams
2013-03-27 6:57 ` Eli Zaretskii
2013-03-27 9:45 ` Dani Moncayo
2013-03-27 12:20 ` Eli Zaretskii
2013-03-27 13:39 ` Drew Adams
2013-03-28 9:25 ` Eli Zaretskii
2013-04-15 7:35 ` Eli Zaretskii
2013-04-15 11:54 ` Juanma Barranquero
2013-04-15 12:30 ` Eli Zaretskii
2013-04-15 12:40 ` martin rudalics
2013-04-15 14:18 ` Eli Zaretskii
2013-04-15 15:53 ` martin rudalics
2013-04-15 16:21 ` Eli Zaretskii
2013-04-15 19:22 ` martin rudalics
2013-04-16 6:08 ` Eli Zaretskii
2013-04-22 16:04 ` Drew Adams
2013-04-22 16:12 ` Juanma Barranquero
2013-04-22 18:05 ` Eli Zaretskii
2013-04-22 18:18 ` Drew Adams
2013-05-04 10:27 ` Eli Zaretskii
2013-05-04 12:27 ` martin rudalics
2013-05-04 12:33 ` Eli Zaretskii [this message]
2013-05-04 12:45 ` martin rudalics
2013-05-04 13:18 ` Eli Zaretskii
2013-05-04 18:59 ` martin rudalics
2013-05-04 14:38 ` Drew Adams
2013-03-27 13:37 ` 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=83vc6ylybi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14062@debbugs.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).