From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Improving Scroll Bar Tools
Date: Sun, 12 May 2024 20:11:51 +0300 [thread overview]
Message-ID: <86cyprymy0.fsf@gnu.org> (raw)
In-Reply-To: <K36ZeMtBKjsmeZ0_twvBIbOiNj5LJpuIVpbSmTliGVDXGCjcIGTMtB--nH5bAO34DkHzMWNjYsNKYn4nAInGkAhm3nBGclBfae5G_id0-c8=@protonmail.com> (message from Heime on Sun, 12 May 2024 16:10:46 +0000)
> Date: Sun, 12 May 2024 16:10:46 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: help-gnu-emacs@gnu.org
>
> On Monday, May 13th, 2024 at 3:01 AM, Eli Zaretskii <eliz@gnu.org> 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.
next prev parent reply other threads:[~2024-05-12 17:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 10:40 Improving Scroll Bar Tools Heime
2024-05-10 12:46 ` Po Lu
2024-05-10 13:28 ` Heime
2024-05-10 13:42 ` Po Lu
2024-05-10 14:09 ` Heime
2024-05-10 22:59 ` Heime
2024-05-11 0:12 ` Heime
2024-05-11 6:54 ` Eli Zaretskii
2024-05-11 7:28 ` Heime
2024-05-11 7:37 ` Heime
2024-05-11 8:36 ` Eli Zaretskii
2024-05-11 8:31 ` Eli Zaretskii
2024-05-11 15:38 ` Heime
2024-05-11 16:29 ` Eli Zaretskii
2024-05-11 23:00 ` Heime
2024-05-12 6:08 ` Eli Zaretskii
2024-05-12 13:51 ` Heime
2024-05-12 15:01 ` Eli Zaretskii
2024-05-12 16:10 ` Heime
2024-05-12 17:11 ` Eli Zaretskii [this message]
2024-05-12 17:28 ` Heime
2024-05-12 17:49 ` Eli Zaretskii
2024-05-15 8:50 ` Jean Louis
2024-05-15 20:16 ` Emanuel Berg
2024-05-18 13:37 ` Heime
2024-05-23 10:30 ` Emanuel Berg
2024-05-15 21:27 ` Heime
2024-05-16 8:43 ` Jean Louis
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cyprymy0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).