unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Improving Scroll Bar Tools
Date: Sat, 11 May 2024 19:29:37 +0300	[thread overview]
Message-ID: <86seyo1fda.fsf@gnu.org> (raw)
In-Reply-To: <NlfwtlLjC6o2810G1yOWQSUs8WGmnNmxgxMEne68rtaaUKEfmLpK7ilnTFOc9R8gaFHALJhQwIibLIxlScLpw_b5yUBwwrMRNrHnQ-B4Ujs=@protonmail.com> (message from Heime on Sat, 11 May 2024 15:38:54 +0000)

> Date: Sat, 11 May 2024 15:38:54 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: help-gnu-emacs@gnu.org
> 
> > You are mixing two different levels of functions. scroll-bar-mode and
> > horizontal-scroll-bar-mode are user commands, whereas
> > set-window-scroll-bars is a Lisp function. If there is a
> > contradiction between them, it is a problem for the user-level
> > functionality which mixes them, and it is up to that user-level
> > functionality (presumably, some code you have written) to fix the
> > problem, whatever it is.
> 
> How do users change the scroll bars of specific windows ?

There's no Emacs feature currently to do that (but maybe there are
third-party packages out there offering such capabilities).

> > Since scroll-bar-mode and horizontal-scroll-bar-mode are minor modes,
> > they each one have a hook, which could be used to turn off
> > window-specific scroll bars. However, I don't recommend that because
> > that would prevent users from having window-specific scroll bars that
> > do not heed to frame-global settings. IOW, you will be coding a
> > feature that works against documented Emacs behavior.
> 
> Ok, you want the minor modes not to affect window-specific scroll bars that
> users customised. 

That is the current arrangement, yes.  Window-specific scroll bars
take precedence over the frame-global settings.



  reply	other threads:[~2024-05-11 16:29 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 [this message]
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
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=86seyo1fda.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).