unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "rms@gnu.org" <rms@gnu.org>
Cc: "andremegafone@gmail.com" <andremegafone@gmail.com>,
	"eliz@gnu.org" <eliz@gnu.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
	"spacibba@aol.com" <spacibba@aol.com>,
	"joaotavora@gmail.com" <joaotavora@gmail.com>
Subject: RE: [External] : Re: fido-vertical bindings
Date: Sat, 21 Aug 2021 05:18:40 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488AEA6692855F2CACC99ACF3C29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <E1mHHZq-0005iM-Iv@fencepost.gnu.org>

> > > > The whole idea or "internal only" is
> > > > inappropriate for free software, IMHO.
> > > Bollocks.
> > Bollocks, IMHO.
> 
> I agree with your position that "internal only" is
> reasonable, with the meaning you conveyed:
> 
> "Internal only", in free software, means "We may change this interface
> at any time.  Please don't call it.  If you do call it, and your code
> breaks, that is not a bug; don't expect us to 'fix' it."
> 
> That is a perfectly legitimate position for a developer to take.

Yes, it is.  And I think it's about what I said:

  All it can mean is that you might not want
  to modify XYZ because at some point Emacs dev
  might change the code so that your code that
  uses that modification no longer does what
  you wrote it to do.

  It's a head-up, to save you trouble dealing
  with possible code changes. Any more limiting
  interpretation of it is misguided, IMO.

It's letting users know that the code might
change at any time - you've been warned not to
expect otherwise.  I don't think it _can_
legitimately mean anything more than that.
It's an aid to users, as a heads-up.  It's not
a "Verboten!" sign.

I wrote in response to this:

 > If the user can modify it then it needs to be
 > a customize.  The users shouldn't modify normal
 > variables as they are intended to be for internal
 > uses only.

If that "should" is meant as "you probably don't
want to do that, and here's why: because you
probably don't want to write code that depends
on code that's likely to change" - then I agree
(for "internal" vars, not "normal" vars).

But if that "should" is meant as something more
than that, then I disagree.  There's nothing
"wrong" with ignoring an "internal only" sign.
There's nothing hidden or walled-off about such
code - and intentionally so, as free software.

If the "only" in "internal only" means we don't
want to encourage dependence on it, then yes.
If the "only" means something more, as in "ours
not yours - hands off!", then no.

And I don't think that "normal variables" are
considered for internal use only.  Most normal
variables aren't flagged as "internal only".
defcustoms aren't the only variables users can,
or "should" be able to, change.

(The old term for options, "user variables",
is even a bit unfortunate, as if only they
were open to use by users.)

There's a lot that can be packed into a little
expression such as "internal only".  Nuances
matter.  A message of "Off limits!" isn't very
helpful, IMO.  A message of "There be dragons!"
can be helpful.


  reply	other threads:[~2021-08-21  5:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210817000745.cpnevwj7anmarue2.ref@Ergus>
2021-08-17  0:07 ` fido-vertical bindings Ergus
2021-08-17 12:08   ` João Távora
2021-08-18 12:25     ` Ergus
2021-08-20  2:21       ` Ergus
2021-08-20  9:55         ` João Távora
2021-08-20 11:46           ` Ergus
2021-08-20 15:27             ` João Távora
2021-08-20 15:41             ` [External] : " Drew Adams
2021-08-20 11:51           ` André A. Gomes
2021-08-20 12:51             ` Ergus
2021-08-20 15:42               ` [External] : " Drew Adams
2021-08-20 15:52                 ` Eli Zaretskii
2021-08-20 16:42                   ` Drew Adams
2021-08-21  3:21                     ` Richard Stallman
2021-08-21  5:18                       ` Drew Adams [this message]
2021-08-20 15:37             ` João Távora
2021-08-20 15:41             ` [External] : " Drew Adams

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=SJ0PR10MB5488AEA6692855F2CACC99ACF3C29@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=andremegafone@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=rms@gnu.org \
    --cc=spacibba@aol.com \
    /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).