From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Heime Newsgroups: gmane.emacs.help Subject: Re: Improving Scroll Bar Tools Date: Sun, 12 May 2024 17:28:17 +0000 Message-ID: <-Yh26eTmdz9XzpeO4CZR1wgjoNtg30sukh85uZn4iOfec6-8rxMb-tk0hcSvFno5b7ha52XsnexdZlcC6aMZenksuPvD-juOw5jRuoqJSvk=@protonmail.com> References: <86seyo1fda.fsf@gnu.org> <86cypr1s0c.fsf@gnu.org> <86le4fysyv.fsf@gnu.org> <86cyprymy0.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15905"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Eli Zaretskii Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun May 12 19:29:08 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 1s6D0W-0003v0-1J for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 12 May 2024 19:29:08 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s6Czs-0000SA-9K; Sun, 12 May 2024 13:28:28 -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 1s6Czq-0000Rn-BN for help-gnu-emacs@gnu.org; Sun, 12 May 2024 13:28:26 -0400 Original-Received: from mail-4324.protonmail.ch ([185.70.43.24]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s6Czo-0004GO-6f; Sun, 12 May 2024 13:28:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1715534901; x=1715794101; bh=Weued2dF7XbnU9bwUi0/sxcXK0Pwj5e4YfncCIu4Am0=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=mjgygsathvWtmHQ0kkhMQoMMfPxqkEBdg1yAAh1KeS//UKWJdlwb3dq5ciznDSn8m hVBBQNXSkeLxgJIefzBMvAsoliGlXfmlDjPPi/2N4nNqwWpnt9VMaEs/ltKtXghcFp +my78sKFpdY3vP9EB3HKmetLLkN7peJuVhjaadOGCDZenQES9/whNmv45UnZoqqdb+ GdLY9TCXKcHwfgT6PFX72+t4HzQjb/US1YtDYAiArVk6hj2cWuSTTK3tIHATpIDYNr PGKHZ9qgxFlxUmBiH1i6OsMu1TM4mhd4BQ+DgAhp+4P8LroTWhInEMzN/zAqr7mxZm GpOu9IjyamLlg== In-Reply-To: <86cyprymy0.fsf@gnu.org> Feedback-ID: 57735886:user:proton X-Pm-Message-ID: 8a765815f1b92059e489000694422b009fd432b9 Received-SPF: pass client-ip=185.70.43.24; envelope-from=heimeborgia@protonmail.com; helo=mail-4324.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:146691 Archived-At: Sent with Proton Mail secure email. On Monday, May 13th, 2024 at 5:11 AM, Eli Zaretskii wrote: > > Date: Sun, 12 May 2024 16:10:46 +0000 > > From: Heime heimeborgia@protonmail.com > > Cc: help-gnu-emacs@gnu.org > >=20 > > On Monday, May 13th, 2024 at 3:01 AM, Eli Zaretskii eliz@gnu.org wrote: > >=20 > > > > How can a package know whether a window-specific setting was introd= uced by > > > > set-window-scroll-bars ? > > >=20 > > > By looking at the value returned by window-scroll-bars. > > >=20 > > > > Would you be kind enough to show the specific use of scroll-bar-mod= e-hook and > > > > its ilk for the purpose you have in mind, so I can develop it ? > > >=20 > > > 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. > >=20 > > Eli, when set-window-scroll-bars have been applied to a window I want t= o know > > some settings were applied. That what you'd like to know. >=20 >=20 > 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. I had missed that line. I would use window-scroll-bars to test the=20 scroll type - nil meaning that frame-globals would function. =20 > > 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 m= odes. >=20 >=20 > 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. >=20 > > 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 t= hing. > > What would be the standard procedure then, to kill or close the window = ? >=20 >=20 > 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. Users would then be required to change the window scroll bar type to nil for them to have frame-global scroll bars to work. Under what group would scroll bar features categorise under ? Would a new package for window specific scroll bars ideally define a minor=20 mode or not ?