From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 19076@debbugs.gnu.org
Subject: bug#19076: 25.0.50; Switching vertical scroll bars off makes the mode line and buffer area disappear
Date: Thu, 20 Nov 2014 11:13:48 +0100 [thread overview]
Message-ID: <m31toyi3hf.fsf@stories.gnus.org> (raw)
In-Reply-To: <546CBCDC.6020602@gmx.at> (martin rudalics's message of "Wed, 19 Nov 2014 16:53:00 +0100")
martin rudalics <rudalics@gmx.at> writes:
> These values look completely normal. Please tell me also the value
> returned by (x-frame-geometry).
((frame-position 0 . 0) (frame-outer-size 598 . 1184) (external-border-size 1 . 1) (title-height . 0) (menu-bar-external) (menu-bar-size 0 . 0) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 596 . 36) (frame-inner-size 596 . 1146))
> Do mode line and echo area reappear when you change the frame size or
> split a window?
If I resize the frame, the mode line and echo area reappears. If I just
split a window, the uppermost window gets a mode line, but there's still
no mode line or echo area in the bottom window.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2014-11-20 10:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:10 bug#19076: 25.0.50; Switching vertical scroll bars off makes the mode line and buffer area disappear Lars Magne Ingebrigtsen
2014-11-18 7:52 ` martin rudalics
2014-11-18 12:38 ` Lars Magne Ingebrigtsen
2014-11-18 15:58 ` Eli Zaretskii
2014-11-18 19:39 ` Lars Magne Ingebrigtsen
2014-11-19 13:18 ` Lars Magne Ingebrigtsen
2014-11-19 13:05 ` Lars Magne Ingebrigtsen
2014-11-19 15:53 ` martin rudalics
2014-11-20 10:13 ` Lars Magne Ingebrigtsen [this message]
2014-11-20 16:03 ` martin rudalics
2014-11-27 13:28 ` Lars Magne Ingebrigtsen
2014-11-27 18:35 ` martin rudalics
2014-11-27 13:30 ` Lars Magne Ingebrigtsen
2014-11-27 18:36 ` martin rudalics
2015-02-13 18:27 ` martin rudalics
2015-02-14 4:17 ` Lars Ingebrigtsen
2016-02-08 6:21 ` Lars Ingebrigtsen
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=m31toyi3hf.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=19076@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).