From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Cc: Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: Is there a way of setting a variable only when it exists?
Date: Tue, 15 Mar 2022 08:49:05 +0100 [thread overview]
Message-ID: <YjBE8UyNt1piImGw@tuxteam.de> (raw)
In-Reply-To: <YjA5ECg5sRHR9iuc@protected.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On Tue, Mar 15, 2022 at 09:58:25AM +0300, Jean Louis wrote:
[...]
> I am trying to understand:
>
> - what is user option?
Small extract from the Fine Emacs Lisp manual:
15.3 Defining Customization Variables
=====================================
“Customizable variables”, also called “user options”, are global
Lisp variables whose values can be set through the Customize
interface. Unlike other global variables, which are defined
with ‘defvar’ (*note Defining Variables::), customizable variables
are defined using the ‘defcustom’ macro. In addition to calling
‘defvar’ as a subroutine, ‘defcustom’ states how the variable
should be displayed in the Customize interface, the values it is
allowed to take, etc.
(C-h i is your friend there).
> - you probably mean a variable that cannot be customized by M-x customize?
>
> - because every Emacs variable is user option for me, anything can be
> customized; I do not know if there are any static variables that
> cannot be changed, probably.
You can, of course, make up your own terminology. But this might make
communication wit others... interesting :)
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-03-15 7:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 6:00 Is there a way of setting a variable only when it exists? Marcin Borkowski
2022-03-14 12:52 ` Eli Zaretskii
2022-03-14 13:16 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-14 13:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 6:17 ` Marcin Borkowski
2022-03-15 6:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 6:58 ` Jean Louis
2022-03-15 7:45 ` Marcin Borkowski
2022-03-15 8:12 ` Jean Louis
2022-03-15 7:49 ` tomas [this message]
2022-03-15 8:13 ` Jean Louis
2022-03-15 8:36 ` tomas
2022-03-15 9:28 ` Jean Louis
2022-03-15 10:01 ` tomas
2022-03-15 11:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 8:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-15 15:33 ` [External] : " Drew Adams
2022-03-15 15:38 ` Drew Adams
2022-03-16 18:32 ` Marcin Borkowski
2022-03-16 0:47 ` Michael Heerdegen
2022-03-16 18:33 ` Marcin Borkowski
2022-03-16 6:02 ` Tomas Nordin
2022-03-16 6:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16 18:34 ` Marcin Borkowski
2022-03-15 6:48 ` Jean Louis
2022-03-14 22:09 ` Michael Heerdegen
2022-03-15 6:16 ` Marcin Borkowski
2022-03-15 7:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-16 0:25 ` Michael Heerdegen
2022-03-16 18:33 ` Marcin Borkowski
2022-03-16 19:25 ` Michael Heerdegen
2022-03-18 5:58 ` Marcin Borkowski
2022-03-16 20:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-03-17 20:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-03-18 5:59 ` Marcin Borkowski
2022-03-18 17:59 ` Jean Louis
2022-03-19 9:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=YjBE8UyNt1piImGw@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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.
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).