From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Improving Scroll Bar Tools Date: Sun, 12 May 2024 20:11:51 +0300 Message-ID: <86cyprymy0.fsf@gnu.org> References: <86plts3g26.fsf@gnu.org> <86seyo1fda.fsf@gnu.org> <86cypr1s0c.fsf@gnu.org> <86le4fysyv.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19799"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 12 19:12:44 2024 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1s6Ckd-0004xT-SF for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 12 May 2024 19:12:44 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s6Cju-0005qr-BD; Sun, 12 May 2024 13:11:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s6Cjq-0005qU-BO for help-gnu-emacs@gnu.org; Sun, 12 May 2024 13:11:54 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s6Cjp-000136-RA for help-gnu-emacs@gnu.org; Sun, 12 May 2024 13:11:54 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=IfGt64sakTfePPn4qT82CrmCfLRrsa4gUlDxlFnTx/I=; b=cxd8kW3BkD7t piFs9UeHbsnhn9m3I5paG7iUrjWp5taDNZc8jbNf7FLXVHCowN2x3gdMU3uRUfp/8srr0TLSQoSCe PSa1u8gIwmgjX8ZzlzlK/6Vnfy27tf9AYaSUUP60Y+HRe4Gb0QKnW7D6OJW/1c0DGMhPRCMh1QtT8 dZNGYcOw4sqDm31M9NJ//bAlUJAH5vC/PKyocNU+de9foU1lShpn3zUa52vs0njzevLzmu8m17Cvd VVdLJu8wIdVVjMm8DxN6F+tW3HkJIV+ielZyvKtEW4pe4xuOqbVnXO8QprgdlP4SU8+JCY2iqBHOu 3PbKz8+Lo1Yn/4p0zdQO2g==; In-Reply-To: (message from Heime on Sun, 12 May 2024 16:10:46 +0000) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:146690 Archived-At: > Date: Sun, 12 May 2024 16:10:46 +0000 > From: Heime > Cc: help-gnu-emacs@gnu.org > > On Monday, May 13th, 2024 at 3:01 AM, Eli Zaretskii wrote: > > > > How can a package know whether a window-specific setting was introduced by > > > set-window-scroll-bars ? > > > > By looking at the value returned by window-scroll-bars. > > > > > Would you be kind enough to show the specific use of scroll-bar-mode-hook and > > > its ilk for the purpose you have in mind, so I can develop it ? > > > > > > Sorry, I don't have time (and I don't really know what you'd like to > > do when frame's scroll-bars are changed). I can describe the idea: in > > the hook function use set-window-scroll-bars to change the > > window-specific scroll bars according to what you want. > > Eli, when set-window-scroll-bars have been applied to a window I want to know > some settings were applied. That what you'd like to know. But I just told you how to do that, above: use window-scroll-bars. Its doc string explains how to know whether a window-specific scroll bars were set for the window by set-window-scroll-bars. > Once a window settings have been changed by set-window-scroll-bars, how can > one release the change and make them once again affected by the minor modes. Use set-window-scroll-bars. Its doc string tells you how to call it so that the window will again use frame-global settings of scroll bars. > In a previous comment, you described that the aforementioned situation might > not be a good idea because their use is not designed for such sort of thing. > What would be the standard procedure then, to kill or close the window ? No, I said that window-specific settings take precedence over frame-globals ones, and that coding a feature that would work otherwise is not recommended.