From: Alan Mackenzie <acm@muc.de>
To: martin rudalics <rudalics@gmx.at>
Cc: 37213@debbugs.gnu.org
Subject: bug#37213: Execute set-window-margins. left-margin-width remains 0.
Date: Sun, 1 Sep 2019 09:48:45 +0000 [thread overview]
Message-ID: <20190901094844.GB16279@ACM> (raw)
In-Reply-To: <af01076e-704b-88b5-bc27-65061d15e0ab@gmx.at>
Hello, Martin.
On Sun, Sep 01, 2019 at 10:26:35 +0200, martin rudalics wrote:
> > Is the read value well-defined? Never having set it, the value it has
> > seems always to be 0.
> All margin-related values are zero by default.
> > But even if it is well-defined, is it useful for
> > anything?
> To keep you informed about the sizes of the margins of a window
> whenever the buffer will be shown in it via 'set-window-buffer'.
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.
> > Yes, that's the thing. We don't have "window local variables" in Emacs,
> > so anything specific to a window needs a function interface with the
> > window being one of the parameters.
> Right. Windows behave like frames in this regard.
> > I've proposed a simple amendment to the "Display Margins" page of the
> > elisp manual, saying "don't use these variables to ....!". This would
> > solve the misunderstanding I experienced earlier.
> 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?
> martin
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-09-01 9:48 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 [this message]
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
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=20190901094844.GB16279@ACM \
--to=acm@muc.de \
--cc=37213@debbugs.gnu.org \
--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).