From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 29279@debbugs.gnu.org
Subject: bug#29279: Sharing the margins
Date: Mon, 13 Nov 2017 21:32:34 +0200 [thread overview]
Message-ID: <83h8tykm99.fsf@gnu.org> (raw)
In-Reply-To: <d9e4b108-c738-73f8-3257-61219ebeee8b@yandex.ru> (message from Dmitry Gutov on Mon, 13 Nov 2017 21:16:30 +0200)
> Cc: 29279@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 13 Nov 2017 21:16:30 +0200
>
> On 11/13/17 8:29 PM, Eli Zaretskii wrote:
>
> >> I'm not sure I understand the "Zero means ..." passage, though.
> >
> > That's your "total width" thing, for margin users that just want to
> > set the overall width of the margins without displaying anything
> > there. Like Joost Kramer's visual-fill-column and similar packages.
>
> OK, but why "maximum width"? workroom-mode wanted to set the total
> width, but if we want to describe what will happen with the column in
> question, the value sounds more like "minimum total width".
Indeed, I meant to write "total", not "maximum".
> > Yes, set-window-margins will most probably be reimplemented by calling
> > the above.
>
> Which area will the left-margin specs be drawn on, then? Ones without
> any particular symbol specified.
Either without any symbol, or with nil, or with some invented symbol.
Something ti figure out as part of the implementation.
> Having ORDINAL = 0 mean something else, not so great. Especially if the
> result is to have the padding in this column, necessary to reach the
> specified total width.
My idea was not to create a column, just make sure the total width is
no less than the requested value. Which means some of the requested
columns will be wider than requested, I guess.
> I imagine workroom-mode might have a idea where they want the padding to
> end up (to the left or to the right of all columns). So instead of
> co-opting the ORDINAL argument to mean "cols will total cols"
We need to study the needs of potential users, no doubt, before
finalizing the API.
> > It will also be somewhat slower.
>
> We should probably measure before discarding this idea.
The slowdown will be caused by resizing of the margins (and all the
window-configuration-change-hooks that triggers).
next prev parent reply other threads:[~2017-11-13 19:32 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 23:51 bug#29279: Sharing the margins Dmitry Gutov
2017-11-13 15:43 ` Eli Zaretskii
2017-11-13 17:24 ` Dmitry Gutov
2017-11-13 18:15 ` Eli Zaretskii
2017-11-13 19:02 ` Dmitry Gutov
2017-11-13 19:22 ` Eli Zaretskii
2017-11-13 19:33 ` Dmitry Gutov
2017-11-13 15:46 ` Eli Zaretskii
2017-11-13 17:54 ` Dmitry Gutov
2017-11-13 18:29 ` Eli Zaretskii
2017-11-13 19:16 ` Dmitry Gutov
2017-11-13 19:32 ` Eli Zaretskii [this message]
2017-11-13 21:16 ` Dmitry Gutov
2017-11-14 15:30 ` Eli Zaretskii
2017-11-14 22:39 ` Dmitry Gutov
2017-11-15 3:42 ` Eli Zaretskii
2017-11-15 14:23 ` Dmitry Gutov
2017-11-15 18:00 ` Eli Zaretskii
2017-11-15 21:49 ` Dmitry Gutov
2017-11-16 15:50 ` Eli Zaretskii
2017-11-18 23:55 ` Dmitry Gutov
2017-11-19 15:34 ` Eli Zaretskii
2017-11-20 22:23 ` Dmitry Gutov
2017-11-21 15:40 ` Eli Zaretskii
2017-11-15 18:51 ` martin rudalics
2017-11-15 20:03 ` Eli Zaretskii
2017-11-15 21:09 ` Dmitry Gutov
2017-11-16 15:39 ` Eli Zaretskii
2017-11-18 23:46 ` Dmitry Gutov
2017-11-19 15:30 ` Eli Zaretskii
2017-11-19 0:47 ` Joost Kremers
2017-11-19 9:20 ` Dmitry Gutov
2017-11-14 9:54 ` martin rudalics
2017-11-14 15:51 ` Eli Zaretskii
2017-11-15 18:50 ` martin rudalics
2017-11-14 9:54 ` martin rudalics
2017-11-14 15:51 ` Eli Zaretskii
2017-11-14 18:30 ` martin rudalics
2017-11-14 19:05 ` Eli Zaretskii
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=83h8tykm99.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29279@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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).