From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: greselin.andrea@gmail.com, 36193@debbugs.gnu.org
Subject: bug#36193: 26.2; 'set-window-scroll-bars' setting doesn't take effect in emacsclient session
Date: Mon, 22 Jul 2019 09:41:16 +0200 [thread overview]
Message-ID: <9790a425-173c-765b-b8a0-8636f7a4c8c9@gmx.at> (raw)
In-Reply-To: <83o91qv1a9.fsf@gnu.org>
tags 36193 fixed
close 36193 27.1
quit
> I think this change needs to be called out in NEWS.
Done.
> If you haven't already, please make sure you test the window-resizing
> stuff on TTY frames, as your changes affect the code which deals with
> that, and we know from bitter experience that it's somewhat fragile.
I had given it some limited testing and I've done a few further tests
now. Inherently, the old behavior was incorrect in a number of ways.
For example, it was impossible to reduce a minibuffer-only frame to
one text line unless horizontal scroll bars were explicitly disabled
for that frame. It's now possible to enable horizontal scroll bars on
minibuffer windows although it does not make much sense.
In either case, thanks for the reminder. Unfortunately, as we know,
frame/window resizing routines depend on too many external factors so
any related changes will always tend to be fragile.
martin, trying to close this bug now
prev parent reply other threads:[~2019-07-22 7:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 14:57 bug#36193: 26.2; 'set-window-scroll-bars' setting doesn't take effect in emacsclient session Andrea Greselin
2019-06-13 16:11 ` Eli Zaretskii
2019-06-13 18:48 ` Andrea Greselin
2019-06-16 8:17 ` martin rudalics
2019-06-18 12:46 ` Andrea Greselin
2019-06-18 13:42 ` martin rudalics
2019-06-18 13:59 ` Andrea Greselin
2019-06-19 9:14 ` martin rudalics
2019-07-17 8:38 ` martin rudalics
2019-07-18 8:12 ` Andrea Greselin
2019-07-19 8:15 ` martin rudalics
2019-07-19 9:09 ` Eli Zaretskii
2019-07-22 7:41 ` martin rudalics [this message]
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=9790a425-173c-765b-b8a0-8636f7a4c8c9@gmx.at \
--to=rudalics@gmx.at \
--cc=36193@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=greselin.andrea@gmail.com \
/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).