unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: window-buffer-change-functions
Date: Fri, 23 Sep 2022 09:12:10 +0300	[thread overview]
Message-ID: <83fsgir551.fsf@gnu.org> (raw)
In-Reply-To: <E1obZE9-0008Vr-N0@fencepost.gnu.org> (message from Richard Stallman on Thu, 22 Sep 2022 23:19:45 -0400)

> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Date: Thu, 22 Sep 2022 23:19:45 -0400
> 
> A variable is supposed to have one value at any given time.  It might
> be the default binding, or a something-local binding.  But regardless
> of why that binding is current at any time, its value is _the value_
> of the variable at that time.  The other bindings shouldn't affect
> what the variable stands for when they are not current.
> 
> Special exceptions that undermine the meaning of a variable's value,
> or any general design principle, cause conceptual confusion that will
> get us in trouble.

I think I agree, but could you please explain why you think this
variable violates that principle?  Because I don't think I see that.



  reply	other threads:[~2022-09-23  6:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SJ0PR10MB54886AFA7B33CF1E43E2E013F39A9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found] ` <83o86hyild.fsf@gnu.org>
     [not found]   ` <877d1ycbom.fsf@gnus.org>
     [not found]     ` <SJ0PR10MB548895C6693206D88C719E60F34C9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]       ` <835yhivx39.fsf@gnu.org>
     [not found]         ` <SJ0PR10MB5488AA81BBFCC4B4CE2D31B4F34C9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]           ` <83v8piuh5k.fsf@gnu.org>
     [not found]             ` <SJ0PR10MB54887366A66613D1189EC466F34C9@SJ0PR10MB5488.namprd10.prod.outlook.com>
     [not found]               ` <2f85eda92184de27e10572e6b2320885@webmail.orcon.net.nz>
     [not found]                 ` <83pmfpv4fs.fsf@gnu.org>
     [not found]                   ` <7110e0330e878c144a6364a8e6ad651c@webmail.orcon.net.nz>
2022-09-21 13:59                     ` window-buffer-change-functions Richard Stallman
2022-09-21 16:22                       ` [External] : window-buffer-change-functions Drew Adams
2022-09-22  6:21                       ` window-buffer-change-functions Eli Zaretskii
2022-09-22  9:44                         ` window-buffer-change-functions martin rudalics
2022-09-23  3:19                           ` window-buffer-change-functions Richard Stallman
2022-09-23  6:12                             ` Eli Zaretskii [this message]
2022-09-24  2:43                               ` window-buffer-change-functions Richard Stallman
2022-09-23 11:13                             ` window-buffer-change-functions Phil Sainty
2022-09-24  2:43                               ` window-buffer-change-functions Richard Stallman

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=83fsgir551.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).