From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: npostavs@gmail.com, emacs-devel@gnu.org
Subject: Re: "after" variable watchers
Date: Thu, 27 May 2021 19:51:50 +0300 [thread overview]
Message-ID: <83pmxc86hl.fsf@gnu.org> (raw)
In-Reply-To: <400a3a6d-3fff-2eef-3fb2-0d758184bd46@gmx.at> (message from martin rudalics on Mon, 24 May 2021 10:47:29 +0200)
> Cc: npostavs@gmail.com, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Mon, 24 May 2021 10:47:29 +0200
>
> >> (1) The desired width of W's left fringe as set by `set-window-fringes'
> >> and stored in a slot w->nominal_left_fringe_width where a value of
> >> -1 stands for "take the width from W's buffer",
> >
> > Side note: could we please NOT call these "nominal" values? "Nominal"
> > means "standard", whereas these aren't. How about "desired" or
> > "requested"?
>
> I've been using "nominal" in the sense expressed by Wikipedia as "From a
> philosophical viewpoint, nominal value represents an accepted condition,
> which is a goal or an approximation, as opposed to the real value, which
> is always present.". That sentence expresses well what I'm trying to do
> here IMHO.
Well, I'm asking you to use a different terminology, because it always
trips me, Wikipedia notwithstanding.
More to the point: the more I think about what you want to do the less
I like it. So I'm going to stop thinking and just say that I don't
think we should do it. I understand the motivation, but I think it's
a slippery slope towards much more complex and hard to maintain code,
with a goal that I believe cannot be reached, only approximated. We
will complicate the heck out of the window-resizing functions, and in
the end will not be able to promise that any change will be
immediately visible through the accessors and variables. E.g., what
happens if redisplay decides to resize the mini-window -- you end up
with at least one window whose dimensions are not what was before.
We don't make such promises now, and with frames AFAIU we cannot even
try promising that (because WMs get in the way). So why complicate
Emacs so much for such ephemeral reasons? I say let's document that
not every change is immediately reflected, until the next redisplay,
and move on to more important developments.
Having said that, you are the expert on this, so if you decide to do
this anyway, I won't fight you or forbid doing that. I just think we
shouldn't do this.
next prev parent reply other threads:[~2021-05-27 16:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 8:27 "after" variable watchers martin rudalics
2021-05-17 10:23 ` Eli Zaretskii
2021-05-17 16:40 ` martin rudalics
2021-05-17 16:57 ` Eli Zaretskii
2021-05-18 15:10 ` martin rudalics
2021-05-20 13:46 ` Eli Zaretskii
2021-05-24 8:47 ` martin rudalics
2021-05-27 16:51 ` Eli Zaretskii [this message]
2021-06-06 7:42 ` martin rudalics
2021-05-17 18:36 ` Stefan Monnier
2021-05-17 18:45 ` Eli Zaretskii
2021-05-17 18:54 ` Stefan Monnier
2021-05-17 18:55 ` Stefan Monnier
2021-05-18 15:10 ` martin rudalics
2021-05-18 15:57 ` Stefan Monnier
2021-05-18 17:01 ` martin rudalics
2021-05-20 13:49 ` Eli Zaretskii
2021-05-24 8:48 ` martin rudalics
2021-05-27 16:53 ` Eli Zaretskii
2021-05-17 14:57 ` Matt Armstrong
2021-05-17 16:41 ` martin rudalics
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=83pmxc86hl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.com \
--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 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.