From: martin rudalics <rudalics@gmx.at>
To: Jean Louis <bugs@gnu.support>, Help GNU Emacs <emacs-devel@gnu.org>
Subject: Re: How to keep window margins after switching buffers?
Date: Sun, 25 Apr 2021 19:12:00 +0200 [thread overview]
Message-ID: <626fa175-c417-9999-afa6-8f65cfa9ac7f@gmx.at> (raw)
In-Reply-To: <courier.0000000060858D9D.000015DF@stw1.rcdrun.com>
> I have rather aesthetical need to have window margins, I use it as:
>
> (set-window-margins (get-buffer-window) 10 10)
>
> But when I switch to other buffer and come back margins disappea.
>
> Would there any way to keep margins for specific buffer even after
> switching?
I suppose you want to set `left-margin-width' and `right-margin-width'
for that buffer instead.
martin
next prev parent reply other threads:[~2021-04-25 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 15:41 How to keep window margins after switching buffers? Jean Louis
2021-04-25 17:12 ` martin rudalics [this message]
2021-04-25 17:34 ` 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=626fa175-c417-9999-afa6-8f65cfa9ac7f@gmx.at \
--to=rudalics@gmx.at \
--cc=bugs@gnu.support \
--cc=emacs-devel@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.
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).