From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#36193: 26.2; 'set-window-scroll-bars' setting doesn't take effect in emacsclient session Date: Tue, 18 Jun 2019 15:42:39 +0200 Message-ID: References: <83lfy5zcqb.fsf@gnu.org> <095ad324-1ba2-253d-9d5d-bb576f722966@gmx.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="143468"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36193@debbugs.gnu.org To: Andrea Greselin Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Jun 18 15:43:11 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hdEOE-000bCc-5u for geb-bug-gnu-emacs@m.gmane.org; Tue, 18 Jun 2019 15:43:10 +0200 Original-Received: from localhost ([::1]:58154 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hdEOD-000334-7p for geb-bug-gnu-emacs@m.gmane.org; Tue, 18 Jun 2019 09:43:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53345) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hdEO7-00032r-Mv for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2019 09:43:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hdEO6-0000u9-EJ for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2019 09:43:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58648) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hdEO6-0000tr-6E for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2019 09:43:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hdEO6-0006OU-2T for bug-gnu-emacs@gnu.org; Tue, 18 Jun 2019 09:43:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 18 Jun 2019 13:43:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36193 X-GNU-PR-Package: emacs Original-Received: via spool by 36193-submit@debbugs.gnu.org id=B36193.156086537624564 (code B ref 36193); Tue, 18 Jun 2019 13:43:02 +0000 Original-Received: (at 36193) by debbugs.gnu.org; 18 Jun 2019 13:42:56 +0000 Original-Received: from localhost ([127.0.0.1]:43959 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hdEO0-0006O7-55 for submit@debbugs.gnu.org; Tue, 18 Jun 2019 09:42:56 -0400 Original-Received: from mout.gmx.net ([212.227.15.18]:41835) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hdENv-0006Nn-IY for 36193@debbugs.gnu.org; Tue, 18 Jun 2019 09:42:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1560865361; bh=/MkZrnVuMizAjPxfGq1v6BN79FZpncK2w7SitVrfhFw=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=RZV1baGCNbo045UsOnjWkWpqxQd3f75z5NqqeDjWQ2T1BvEYPXo0HRH7fWEKGauf+ Dhpc6IXCclsfZARDfel3pYnT+oC0g+jj0jNJcKHkiCDNKdCJNlYMAadpRWU19v43TW OixDQqPfuzenMU2k6EDANbr5xuoHM8WVyE2jN7kQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([212.95.5.226]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0LiTm8-1iBBgz2J1I-00ceFq; Tue, 18 Jun 2019 15:42:41 +0200 In-Reply-To: Content-Language: de-DE X-Provags-ID: V03:K1:obwEQtsX+57ofZSuKxJpsoQh5L2lBy9uhUMoWEnd9pRgXxJlwNM bv/E6+qvcKoizl5YguI6N8kSCdacpJJLEST/zv1nRGtfgVeBKjA7l3IZCZh2scOUyZP+KMk HgE1sjCZ/ZIQNsbGcHl/HtAz4SjWs645MXsCelJweZ7kHqNAMsBbGEgb00lESVGWaD/x/mB n6ooBlHE8TTGs5HNl9KJA== X-UI-Out-Filterresults: notjunk:1;V03:K0:enWhiDXqItE=:Lo2qC4nbmk3JG58pp/UuTq np8mpLxJgNbsyxpxMhU0Is+k4KBfCdmWOFLYaqZnwC/c715wg41AvPMyZQ54b0/kpPYZdgap0 hU7+5VO80zbXz9GsDzxQ/b62enwiTyvpBlksAYdb2g+jz7nN0BqkvYeMeCGr69/OEyEZYvCrg daM2OKkITwSPYc9LkWKlRdu33LpplfAbHetJCgvGDtCi7pGnQCBgMXvYifI0U19xkZvdpBaJh x8aAh28/SqSM87Sl1g4UPI/xc3rh8GhSteJllE6En4HPTFm+iQ7O25yxw/4kw/uy+NX8VzuPW W1n4rCuymZFpkRB03bhq7eHcQ3y9MHMlxtlym7abtTyHW1/S1sf1uhjIi63gpF07ZUzWwxSvx ne4TRMmVdl5lwzIBdcvGSaNkt2lSIzmyf1OKhx205Fwx4yI2WqkawelIkWH+uiJuXVUKHzCRE 9qDvzcd3aj2IZ63QX+PaQcPEVKvmlT41U6DuU7Xl9OR4Z4/T3tMlbdrDP3cQVNh1vu2DjQnus xpFwtMQHYfASWSx+nILcLUJ4qmmGraBf6GItI5PNkesBW9m5alYw4zM/md9zDBQvh8ZcVgQZf mpgaKL+RVhbeac26V63S+iUdiPPvdtpbjSkQe/2+4I9ZlDUT4FN5MCiWCWkc7oubtUann4S++ +ylqf8PSK4XBWELQ4VHwJ9E84fxNIOpRl8v6EgyZXO0TSKAAvHYa5iEdZfX5I3Bzo3NHrq+PX N3Fj3TjdtkO1quHRLEC3R5rZvgA6CCJYfXzaaeWnDcPFSBJDH4ctVz+3e597jxPb0FBkovWm X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:160768 Archived-At: > Yes. If in 'hide-minibuffer-scrollbar' I replace '(minibuffer-window)'= with > 'nil', the scratch buffer has no scroll bars and they don't reappear e= ven > 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 pers= ist. Ahh... I should have asked you that so it's good you noticed it. This shows that the behavior is not minibuffer window specific. > 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. So showing another buffer in the minibuffer window reenables the scroll bars. This is consistent with the first observation. The behavior (which I would call a bug) is caused by set_window_buffer when called with keep_margins_p nil and is completely unrelated to whether you do it in emacsclient or in a "normal" session. That is if I evaluate with emacs -Q (set-window-scroll-bars (minibuffer-window) 0 nil) and then type M-x, I get the scroll bars back just as you do. The behavior is described in the Elisp manual on 'set-window-scroll-bars' The values specified here may be later overridden by invoking =E2=80=98set-window-buffer=E2=80=99 (*note Buffers and Windows::) o= n WINDOW with its KEEP-MARGINS argument =E2=80=98nil=E2=80=99 or omitted. but I consistently forget about it. If people agree that this is a bug, we can try to find a more general fix. Otherwise, I'll fix the minibuffer window scroll bars with the help of a separate variable (I have written the code some time ago and would "only" have to find it now). As a temporary workaround you can try to set the buffer local values of 'scroll-bar-width' to zero in all buffers that might eventually show up in the minibuffer window, for example, thusly (progn (set-window-scroll-bars (minibuffer-window) 0 nil) (with-current-buffer (get-buffer-create " *Echo Area 0*") (setq scroll-bar-width 0)) (with-current-buffer (get-buffer-create " *Echo Area 1*") (setq scroll-bar-width 0)) (with-current-buffer (get-buffer-create " *Minibuf-0*") (setq scroll-bar-width 0)) (with-current-buffer (get-buffer-create " *Minibuf-1*") (setq scroll-bar-width 0))) This should work as long as you don't enable recursive minibuffers. martin