From: Yuri Khan <yuri.v.khan@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
markus.triska@gmx.at, Emacs developers <emacs-devel@gnu.org>
Subject: Re: PATCH: make linum.el play nicely with other margin-setting extensions
Date: Mon, 16 Nov 2015 15:24:17 +0600 [thread overview]
Message-ID: <CAP_d_8XHBMh+vTMubHK9JMRhpV_8zPzXSm9oy3tjf0GoLWi9cw@mail.gmail.com> (raw)
In-Reply-To: <m237w78hv4.fsf@gmail.com>
On Sun, Nov 15, 2015 at 8:19 PM, João Távora <joaotavora@gmail.com> wrote:
> - ;; FIXME: The interaction between different uses of the margin is
> - ;; problematic. We should have a way for different packages to indicate (and
> - ;; change) their preference independently.
>
> Meaning that we do need to find a way to p *both* nlinum.el and
> darkroom.el to use some kind of ownership-awareness scheme.
Did anyone consider that the proper metaphor may not be ownership but
suballocation? E.g. modes declare how much they want from which side
and with what priority, and the window takes the sums of that. The
margins are then painted from inside outwards, in the order of
decreasing priority. (In this model, “greedy” modes such as darkroom
should have lowest priority so they only get whatever is left over.)
next prev parent reply other threads:[~2015-11-16 9:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 12:23 PATCH: make linum.el play nicely with other margin-setting extensions João Távora
2015-11-12 16:24 ` Eli Zaretskii
2015-11-13 8:32 ` João Távora
2015-11-13 12:23 ` Juanma Barranquero
2015-11-14 8:53 ` Eli Zaretskii
2015-11-15 14:19 ` João Távora
2015-11-15 19:39 ` Eli Zaretskii
[not found] ` <CALDnm521uDOtxE407+pWnq6W=SLLndxp+xmJ1Twtjz3wub8oiQ@mail.gmail.com>
[not found] ` <jwvpoza3g89.fsf-monnier+Inbox@gnu.org>
2015-11-17 22:35 ` bug#20674: " João Távora
2017-11-04 14:42 ` Noam Postavsky
2015-11-16 9:24 ` Yuri Khan [this message]
[not found] ` <CALDnm53Gkm7p2-O-xYf4xMBYPM8sqt2bG5ug-tZu3RKAUE1-gw@mail.gmail.com>
[not found] ` <CAP_d_8VPyasNi21JKMRX+Hz55G5-CwtXuwS3FjXx4Ucp3UDKew@mail.gmail.com>
[not found] ` <CALDnm50EPe8HCucQEnHPadDHwVmgjN8DmeJ+kvh2Nbtb2tYeZw@mail.gmail.com>
[not found] ` <CAP_d_8UjQQuM_45dzUWCGL6Y=3vJ+uZayyqSz1k+sAFmLEN-VQ@mail.gmail.com>
2015-11-16 14:49 ` João Távora
2015-11-13 10:01 ` martin rudalics
2015-11-13 11:11 ` João Távora
2015-11-13 14:53 ` martin rudalics
2015-11-13 15:32 ` João Távora
2015-11-14 8:27 ` martin rudalics
2015-11-14 19:55 ` João Távora
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=CAP_d_8XHBMh+vTMubHK9JMRhpV_8zPzXSm9oy3tjf0GoLWi9cw@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--cc=markus.triska@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 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.