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: Sun, 16 Jun 2019 10:17:37 +0200 Message-ID: <095ad324-1ba2-253d-9d5d-bb576f722966@gmx.at> References: <83lfy5zcqb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="18898"; mail-complaints-to="usenet@blaine.gmane.org" Cc: 36193@debbugs.gnu.org To: Andrea Greselin , Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Jun 16 10:19:47 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 1hcQOB-0004pR-LF for geb-bug-gnu-emacs@m.gmane.org; Sun, 16 Jun 2019 10:19:47 +0200 Original-Received: from localhost ([::1]:38102 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcQOA-0005Ku-Gq for geb-bug-gnu-emacs@m.gmane.org; Sun, 16 Jun 2019 04:19:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57390) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hcQMf-0005KN-19 for bug-gnu-emacs@gnu.org; Sun, 16 Jun 2019 04:18:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hcQMX-00036L-At for bug-gnu-emacs@gnu.org; Sun, 16 Jun 2019 04:18:10 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:54355) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hcQMU-00032U-03 for bug-gnu-emacs@gnu.org; Sun, 16 Jun 2019 04:18:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hcQMT-00079B-QR for bug-gnu-emacs@gnu.org; Sun, 16 Jun 2019 04:18:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 16 Jun 2019 08:18:01 +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.156067306927453 (code B ref 36193); Sun, 16 Jun 2019 08:18:01 +0000 Original-Received: (at 36193) by debbugs.gnu.org; 16 Jun 2019 08:17:49 +0000 Original-Received: from localhost ([127.0.0.1]:39666 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hcQMH-00078i-0q for submit@debbugs.gnu.org; Sun, 16 Jun 2019 04:17:49 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:35603) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hcQMF-00078R-Hn for 36193@debbugs.gnu.org; Sun, 16 Jun 2019 04:17:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1560673057; bh=a/tnc031u6iV0WIgBOokYWu6zPRUNCYbtSrSotiYwYA=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=VDdbguqQu4i8ADXRoFOFz5CKq7/DXg1jWwmFSoqSTeDt+J6mbmur+p62l97al044l lrQJ8dQ8nxv8TH+uddp3HSyHeroYCslJFLdh7fqfjc4C/qUl7/6S6S864BQr+RTEDw AcW8sR0S935fhhEMbIH2Wd9Lq95FnxceZsGjbcDQ= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Original-Received: from [192.168.1.101] ([46.125.249.103]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MGhyc-1hq7T03x5e-00Ds3G; Sun, 16 Jun 2019 10:17:37 +0200 In-Reply-To: Content-Language: de-DE X-Provags-ID: V03:K1:+x6OqblVbSZX9glhjDiPsDMW9ISPCdgp1IBUvCA7xoyj+y/KXfV U9MgIzYqU8oI6l/uBtxlkUG/ILtIDa/6dlhbEepkwKpsBW5ZyL3jSxASKjvoPDG0exXTh4J aW51swmyWKjQS7PKdos7AgunHgQ7+HWcqkVRKhFqIfXpdj8jSZfwzG4I8UX5mjr+Sx0O4Sy AX/Aw6rCk2KvxWf2x9GxQ== X-UI-Out-Filterresults: notjunk:1;V03:K0:5+GcJdGb/QI=:eizcTpJ9drF8SNQMkXBRp0 U/UFn6Z7HhmnYK/KBCfvlhC5eF+t1k19qayvuBFqsUKEjClFXI5V6xG0F2C70zvT31tIPKlof sgyAK3Yeitj11iJZUjVNUyLyRPkaimSuTHVGV+o1jMvasbob0C1d2FgD0pKE0JEHqKY49DFLl vylAHWTzqGuxJBGI/muasoPSH/FZMgx3FYy5lsfh68gnaP5dW3dc86yKdzUb4PDD9b2p5Jdam m9epBPgRxMHFW7j+XlmDha+/DzVmFwU0S8f1291FR7DrZjunrILvH4GG3f0DtyurOoDm9jW/6 Ba0jjgX6bTj7Y7Gw5a3X9nvsa9UwSqT6dxv9QUibzEDMybWySAjuaW+fiCwVNCPbLvs2OSzWh DoUg0Hd4hnGWn71U3sXUPYwszJjvzqS7s0+WWU4Ihk6IGWsUaweQh1HbqIXNu3Jhdjwz0/+2f QKR9MME0FwIvS2CebYFjWDphZDDXP0qglK3gkQeVQWx1zp243/dW2YQ1l1KJi3UvCocDT1t3z QHfN26rK0BTOordourVv4Xn3PXBxBHH9qvBrwaKUXqRBkzgLem/Xf6+GNhZ+9fYsyDBW6yPRV g2sKv4h9za4vJ/XDM1MxypjO213Pum0vo4HQ4vi1nGU2l7RrghdlWxBf/OdFp+RvXgkmmbK3A +uEB/apztqwzdjcbdHW2piuAFH8vD8+QxLHyIVBztZi/8RKWwVwOKhcLK2kRXL1VAoYKZiEoU pSo0BYg17IMbjadtSaQOBALRZYhYtBfipLx1n1tVUX3khaoxMe9GiZjwMSmcVPVrinZtX8Vm 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:160654 Archived-At: > 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