From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>
Cc: 37213@debbugs.gnu.org
Subject: bug#37213: Execute set-window-margins. left-margin-width remains 0.
Date: Thu, 29 Aug 2019 09:46:54 +0200 [thread overview]
Message-ID: <263050b1-8a57-dd39-bd49-88913935f96e@gmx.at> (raw)
In-Reply-To: <20190828195706.GB4530@ACM>
> The documentation says "This variable specifies the width of the left
> margin". As best, this is unclear. What you're saying is that the
> variable ceases to specify that width, should the margin be altered by
> other means.
Eli didn't say that.
> I maintain that this is either a bug in the documentation, or in the
> code.
>
> If the former, it should explicitly state that the variable is
> write-only, and its read value is undefined. It should say that the
> function window-margins should be used instead.
The variable is not write-only and its read value is well-defined.
> But it might be easier just to amend the code. There appear to be just
> two ways to set the width of the left margin (or the right margin), so
> if it gets set the second way, why not just set that variable? Could
> this do any harm? (Note: I haven't looked at the code, yet.)
Please re-read the documentations of 'left-margin-width' and
'set-window-margins' having in mind that the same buffer may appear in
different windows and the same window may show different buffers all
with differing margins.
Once you've done that, please look at the respective documentations
for fringes and scroll bars which are even more complicated because
they have to obey a frame parameter as well.
Thanks, martin
next prev parent reply other threads:[~2019-08-29 7:46 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 [this message]
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
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=263050b1-8a57-dd39-bd49-88913935f96e@gmx.at \
--to=rudalics@gmx.at \
--cc=37213@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@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 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.