From: Andrea Greselin <greselin.andrea@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 36193@debbugs.gnu.org
Subject: bug#36193: 26.2; 'set-window-scroll-bars' setting doesn't take effect in emacsclient session
Date: Tue, 18 Jun 2019 14:46:15 +0200 [thread overview]
Message-ID: <CAJ_oJbb5TW1dHrTE4DJD-Q6tTRC=FzKWYEP+guN6rKLoa1=czg@mail.gmail.com> (raw)
In-Reply-To: <095ad324-1ba2-253d-9d5d-bb576f722966@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 3199 bytes --]
> (1) Is this behavior special for the minibuffer window? That is, if
> in 'after-make-frame-functions' you removed the scroll bar from any
> other window, does it stay removed when you switch to that window
> repeatedly?
Yes. If in 'hide-minibuffer-scrollbar' I replace '(minibuffer-window)' with
'nil', the scratch buffer has no scroll bars and they don't reappear even
if the buffer become longer than the window height. They are only
re-enabled if I open another buffer in that window, and then they persist.
> (2) Does showing a message in the echo area suffice to make the scroll
> bar reappear? With other words, what does "use" the minibuffer stand
> for?
No, messages are shown at startup without the scroll bars being shown. if I
do M-x or M-: or anything that moves the point to the minibuffer, then they
are re-enabled.
> (3) I suppose "it isn't removed afterwards" means you can still remove
> the scroll bar explicitly via 'set-window-scroll-bars' afterwards.
> Right? And if you do that, does it come back after yet another "use"
> of the minibuffer?
Yes I can still remove them by evaluating '(set-window-scroll-bars
(minibuffer-window) 0 nil)'. Then they are only shown while the minibuffer
is active (which is the same behaviour I get right from the start in normal
(non-client) Emacs sessions).
> (4) Can you influence the behavior by customizing the variable
> `resize-mini-windows'?
Nope, it doesn't appear to have any effect, neither when set in the init
file nor in a running emacsclient session.
Best, andrea
On Sun, 16 Jun 2019 at 10:17, martin rudalics <rudalics@gmx.at> wrote:
> > Trying to follow your suggestion I've written
> >
> > (defun hide-minibuffer-scrollbar (frame)
> > (with-selected-frame frame
> > (set-window-scroll-bars (minibuffer-window) 0 nil)))
> > (if (daemonp)
> > (add-hook 'after-make-frame-functions
> #'hide-minibuffer-scrollbar) ; Only for client sessions
> > (set-window-scroll-bars (minibuffer-window) 0 nil))
> >
> > Now client sessions start without the minibuffer scrollbar, but as soon
> as
> > I use the minibuffer it comes back and it isn't removed afterwards.
>
> Scrollbar management in the minibuffer window might be unpredictable.
> Also, GTK builds usually hide the scroll bar in a one line minibuffer
> window automatically, so even the 'min-slider-length' might come into
> play here.
>
> To make sure we don't miss anything before proceeding further:
>
> (1) Is this behavior special for the minibuffer window? That is, if
> in 'after-make-frame-functions' you removed the scroll bar from any
> other window, does it stay removed when you switch to that window
> repeatedly?
>
> (2) Does showing a message in the echo area suffice to make the scroll
> bar reappear? With other words, what does "use" the minibuffer stand
> for?
>
> (3) I suppose "it isn't removed afterwards" means you can still remove
> the scroll bar explicitly via 'set-window-scroll-bars' afterwards.
> Right? And if you do that, does it come back after yet another "use"
> of the minibuffer?
>
> (4) Can you influence the behavior by customizing the variable
> `resize-mini-windows'?
>
> Thanks, martin
>
[-- Attachment #2: Type: text/html, Size: 4303 bytes --]
next prev parent reply other threads:[~2019-06-18 12:46 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ_oJbb5TW1dHrTE4DJD-Q6tTRC=FzKWYEP+guN6rKLoa1=czg@mail.gmail.com' \
--to=greselin.andrea@gmail.com \
--cc=36193@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.