From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: agrambot@gmail.com, 27091@debbugs.gnu.org
Subject: bug#27091: Request: Toggle scroll bar on each window separately
Date: Sat, 27 May 2017 13:35:28 +0300 [thread overview]
Message-ID: <83bmqeio3z.fsf@gnu.org> (raw)
In-Reply-To: <59294DA4.3040700@gmx.at> (message from martin rudalics on Sat, 27 May 2017 11:57:56 +0200)
> Date: Sat, 27 May 2017 11:57:56 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: agrambot@gmail.com, 27091@debbugs.gnu.org
>
> > I think this should be added to the documentation in the ELisp manual.
>
> The doc-string of ‘set-window-buffer’ has this:
>
> Optional third argument KEEP-MARGINS non-nil means that WINDOW's current
> display margins, fringe widths, and scroll bar settings are preserved;
> the default is to reset these from the local settings for BUFFER-OR-NAME
> or the frame defaults.
>
> The Elisp doc of ‘set-window-buffer’ has this:
>
> By default, this function resets WINDOW's position, display
> margins, fringe widths, and scroll bar settings, based on the local
> variables in the specified buffer. However, if the optional
> argument KEEP-MARGINS is non-`nil', it leaves the display margins
> and fringe widths unchanged.
>
> I can amend the last sentence. What else do you want to add?
The above are just fine. The problem is on the other end: the
set-window-scroll-bars function doesn't mention that switching buffers
in the window for which that function was called will reinstate the
scroll bar. (It also doesn't say what is the meaning of
VERTICAL-TYPE's nil value.) And neither does the manual.
next prev parent reply other threads:[~2017-05-27 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 22:01 bug#27091: Request: Toggle scroll bar on each window separately Alex
2017-05-27 8:16 ` martin rudalics
2017-05-27 8:37 ` Eli Zaretskii
2017-05-27 9:06 ` martin rudalics
2017-05-27 9:28 ` Eli Zaretskii
2017-05-27 9:57 ` martin rudalics
2017-05-27 10:35 ` Eli Zaretskii [this message]
2017-05-27 13:26 ` martin rudalics
2017-05-27 13:43 ` Eli Zaretskii
2017-05-27 17:43 ` Alex
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=83bmqeio3z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27091@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=rudalics@gmx.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).