From: "João Távora" <joaotavora@gmail.com>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: Ergus <spacibba@aol.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: fido-vertical bindings
Date: Fri, 20 Aug 2021 16:37:35 +0100 [thread overview]
Message-ID: <CALDnm50USR6_cS4OrNDvs+MCdgU3ROzo3umGbdLqiEjfk=-tJw@mail.gmail.com> (raw)
In-Reply-To: <87czq8tju3.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Fri, Aug 20, 2021, 12:51 André A. Gomes <andremegafone@gmail.com> wrote:
> João Távora <joaotavora@gmail.com> writes:
>
> Interesting. I'm just wondering, how does one decide what should be a
> variable and a customize?
>
I usually make variables and let others decide for me whether to "upgrade"
them. Another criteria is try to imagine it's there's any scenario where a
program might way to set that variable automatically. If there is, I'll
make a normal variable (and then again let other custom.el lovers worry
about the upgrading). Else I'll do the defcustom myself. If I'm creating a
very similar variable in form and function to another one, I'll follow
whichever style it has.
João
[-- Attachment #2: Type: text/html, Size: 1565 bytes --]
next prev parent reply other threads:[~2021-08-20 15:37 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
2021-08-20 15:37 ` João Távora [this message]
2021-08-20 15:41 ` 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='CALDnm50USR6_cS4OrNDvs+MCdgU3ROzo3umGbdLqiEjfk=-tJw@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=andremegafone@gmail.com \
--cc=emacs-devel@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).