From: Drew Adams <drew.adams@oracle.com>
To: Ergus <spacibba@aol.com>, "André A. Gomes" <andremegafone@gmail.com>
Cc: "João Távora" <joaotavora@gmail.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: fido-vertical bindings
Date: Fri, 20 Aug 2021 15:42:17 +0000 [thread overview]
Message-ID: <SJ0PR10MB548874448038FDD4F631914EF3C19@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <20210820125137.qwdlfhjv5a26edgv@Ergus>
> 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.
Wrong. The whole idea or "internal only" is
inappropriate for free software, IMHO.
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.
User options and faces (the things we provide
Customize for) are _conveniences_. Customize
exists for a reason, and that reason is not
to imprison users in a corral of only some
variables.
(Just one opinion.)
next prev parent reply other threads:[~2021-08-20 15:42 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 ` Drew Adams [this message]
2021-08-20 15:52 ` [External] : " Eli Zaretskii
2021-08-20 16:42 ` Drew Adams
2021-08-21 3:21 ` Richard Stallman
2021-08-21 5:18 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB548874448038FDD4F631914EF3C19@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=andremegafone@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--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 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.