From: Eli Zaretskii <eliz@gnu.org>
To: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
Cc: emacs-devel@gnu.org
Subject: Re: Question on set-window-margins
Date: Tue, 02 Jan 2024 21:20:51 +0200 [thread overview]
Message-ID: <83il4bzgmk.fsf@gnu.org> (raw)
In-Reply-To: <m2ttnv1u2p.fsf@inria.fr> (nicolas.rougier@inria.fr)
> From: "Nicolas P. Rougier (inria)" <nicolas.rougier@inria.fr>
> Date: Tue, 02 Jan 2024 18:58:51 +0100
>
>
> When I set margins on a window using 'set-window-margins', it
> works as expected until I switched to another buffer and margins
> are then reset to 0 on both sides. If I switch back to the
> original buffer, margins stay at 0. Does that mean that margins
> are not "attached" to the window nor to the buffer ?
>
> The name of the function suggest it is attached to window (even
> though nothing is really specified in the documentation) but I
> wonder if the 'set-window-margins' is actually meant to be
> transient ?
>
> To keep margins attached to a buffer, I'm using the
> 'window-state-change-hook' and a buffer local margin definition
> but maybe I missed a point.
From the ELisp manual:
-- Function: set-window-margins window left &optional right
This function specifies the margin widths for window WINDOW, in
character cell units. The argument LEFT controls the left margin,
and RIGHT controls the right margin (default ‘0’).
If WINDOW is not large enough to accommodate margins of the desired
width, this leaves the margins of WINDOW unchanged.
The values specified here may be later overridden by invoking
‘set-window-buffer’ (*note Buffers and Windows::) on WINDOW with
its KEEP-MARGINS argument ‘nil’ or omitted.
next prev parent reply other threads:[~2024-01-02 19:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 17:58 Question on set-window-margins Nicolas P. Rougier (inria)
2024-01-02 19:20 ` Eli Zaretskii [this message]
2024-01-02 19:46 ` Nicolas P. Rougier (inria)
2024-01-03 3:23 ` Eli Zaretskii
2024-01-03 3:42 ` Yuan Fu
2024-01-03 5:50 ` Nicolas P. Rougier (inria)
2024-01-03 13:15 ` Eli Zaretskii
2024-01-03 14:05 ` Nicolas P. Rougier (inria)
2024-01-03 16:46 ` Eli Zaretskii
2024-01-03 17:24 ` Nicolas P. Rougier (inria)
2024-01-03 17:28 ` Eli Zaretskii
2024-01-03 17:56 ` Nicolas P. Rougier (inria)
2024-01-03 21:52 ` Jeremy Bryant
2024-01-04 8:53 ` Nicolas P. Rougier (inria)
2024-01-03 15:11 ` John Yates
2024-01-03 16:49 ` Eli Zaretskii
2024-01-03 20:07 ` [External] : " Drew Adams
2024-01-04 12:29 ` John Yates
2024-01-04 12:52 ` Eli Zaretskii
2024-01-05 0:25 ` Yuan Fu
2024-01-05 8:01 ` Eli Zaretskii
2024-01-06 4:35 ` Richard Stallman
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=83il4bzgmk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=nicolas.rougier@inria.fr \
/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).