From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29279@debbugs.gnu.org, joostkremers@fastmail.fm
Subject: bug#29279: Sharing the margins
Date: Wed, 15 Nov 2017 16:23:01 +0200 [thread overview]
Message-ID: <77ddb7fc-d57f-05fa-026c-e23e3bcd3432@yandex.ru> (raw)
In-Reply-To: <83efp0jjhi.fsf@gnu.org>
On 11/15/17 5:42 AM, Eli Zaretskii wrote:
>> It might be just a matter of interpretation: even if all the padding is
>> on the right, the "rightmost" column will remain such, among all the
>> visible columns.
>
> Yes, but "being the rightmost" might mean "being right next to the
> text", for whatever purposes.
So far, I doubt it's going to come up as a real, hard requirement. But
we'll probably see.
> A stretch of white space between the
> text and the margin display might not be what the package wants.
OK, can we think of a case where a package might want its margin content
to be _as far away_ from the text as possible? And become troubled if
some padding stands between it and the window edge?
If not, let's put all padding on the outside and be done with that concern.
>> But the effects are almost entirely the same, aren't they? Both the
>> change of margin width and the change of line numbers column width force
>> the reflowing of buffer contents display.
>
> Again, as long as the text-area dimensions didn't change, it could be
> argued that the hook shouldn't run.
That's some creative nomenclature lawyering. :-)
OK then, what's the practical problem with saying that margins are also
part of "text-area dimensions"?
next prev parent reply other threads:[~2017-11-15 14:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77ddb7fc-d57f-05fa-026c-e23e3bcd3432@yandex.ru \
--to=dgutov@yandex.ru \
--cc=29279@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joostkremers@fastmail.fm \
/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.