From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>
Cc: 37213@debbugs.gnu.org
Subject: bug#37213: Execute set-window-margins. left-margin-width remains 0.
Date: Sun, 1 Sep 2019 14:19:37 +0200 [thread overview]
Message-ID: <b6208011-28f8-b245-dc6f-5fa2e4c98c04@gmx.at> (raw)
In-Reply-To: <20190901094844.GB16279@ACM>
> OK. It seems there are two alternative strategies for manipulating a
> window's margins. One is to use set-window-margins together with
> window-margins, the other is to use left/right-margin-width and
> set-window-buffer.
Right. With fringes and scroll bars you can additionally set a frame
parameter. I know that you're not interested in the latter but any
descriptions should be consistent.
>> Hmm... What is the "current width of the left or right margin"?
>
> I'm not sure I understand the question. In a given window with a left
> margin, there will be a maximum length of string which can be displayed
> in that margin. That is its "current width". The same for a right
> margin. What are you getting at, here?
That you omitted the "In a given window" preamble in the manual. When
you have a frame with two windows showing one and the same buffer, the
margins of these windows can have different widths. What would be the
"current width" in that case?
martin
next prev parent reply other threads:[~2019-09-01 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 18:53 bug#37213: Execute set-window-margins. left-margin-width remains 0 Alan Mackenzie
2019-08-28 19:14 ` Eli Zaretskii
2019-08-28 19:57 ` Alan Mackenzie
2019-08-29 6:42 ` Eli Zaretskii
2019-08-31 11:59 ` Alan Mackenzie
2019-08-31 12:13 ` Eli Zaretskii
2019-08-29 7:46 ` martin rudalics
2019-08-31 14:07 ` Alan Mackenzie
2019-09-01 8:26 ` martin rudalics
2019-09-01 9:48 ` Alan Mackenzie
2019-09-01 12:19 ` martin rudalics [this message]
2019-09-01 12:42 ` Alan Mackenzie
2019-08-29 7:46 ` martin rudalics
[not found] ` <handler.37213.B.156701844019660.ack@debbugs.gnu.org>
2019-08-31 14:39 ` Alan Mackenzie
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b6208011-28f8-b245-dc6f-5fa2e4c98c04@gmx.at \
--to=rudalics@gmx.at \
--cc=37213@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.