unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: fido-vertical bindings
Date: Fri, 20 Aug 2021 16:27:21 +0100	[thread overview]
Message-ID: <CALDnm50pX8pHYrvH+mb8genXynJOsvXvVbOGNJpUXz4SzRYi6A@mail.gmail.com> (raw)
In-Reply-To: <20210820114640.uee6me5pk3ydopek@Ergus>

[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]

On Fri, Aug 20, 2021, 12:47 Ergus <spacibba@aol.com> wrote:

>No-one ever made it a customized variable.  I dislike too many customize
> >variables,
> That's the emacs way ;)
>

No, it's the custom.el way, which is a part of emacs, and which many users
like. Many others don't.

>but I don't oppose this one.
> >
> But if a variable can be safely changed by the user, then it must be a
> custom,


No. Not necessarily. There is, to the best of my understanding, no such
orthodoxy in Emacs. Maybe some other maintainer can correct me.

otherwise the variable is intended for internal use
> right? So the "good" users assume they shouldn't touch it.
>

No. The emacs user manual prescribes other ways to change variables, on
occasion. There is no such orthodoxy. Putting -- in a variable's prefix is
the way to mark it as intended for internal use.

This is why the initial attempt implementation I did for
> icomplete-vertical used to check if there were newlines in
> icomplete-separator; to respect somehow the user preferences and not add
> new customs.
>

In my experience, that kind of complexity to try to achieve custom.el
purity is always unwarranted.

>Users can set non-customizable variables
> But are harder to discover. The defcustom infrastructure and the

customize-* functions help us,
>

There are many means to discover variables and user visible structures.
That has been discussed at length here recently, so I won't repeat that
discussion.

João

>

[-- Attachment #2: Type: text/html, Size: 3257 bytes --]

  reply	other threads:[~2021-08-20 15:27 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 [this message]
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
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=CALDnm50pX8pHYrvH+mb8genXynJOsvXvVbOGNJpUXz4SzRYi6A@mail.gmail.com \
    --to=joaotavora@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).