From: Jean Louis <bugs@gnu.support>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org, Emanuel Berg <moasenwood@zoho.eu>
Subject: Re: Is there a way of setting a variable only when it exists?
Date: Tue, 15 Mar 2022 12:28:25 +0300 [thread overview]
Message-ID: <YjBcOXsenpytuuKS@protected.localdomain> (raw)
In-Reply-To: <YjBQD7dnCiXkUoYh@tuxteam.de>
* tomas@tuxteam.de <tomas@tuxteam.de> [2022-03-15 11:38]:
> On Tue, Mar 15, 2022 at 11:13:19AM +0300, Jean Louis wrote:
> > * tomas@tuxteam.de <tomas@tuxteam.de> [2022-03-15 10:50]:
> > > > - 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 :)
> >
> > No, it was misunderstanding on my side. Now it is clear.
>
> Understood. Perhaps that was a lame attempt at humour on my part.
I totally understand it, people introducing their own understanding of
definitions will have troubles communicating with others, it causes
conflicts.
First we have to agree on what is the accepted definition. There is
nothing wrong in changing such definitions, though it goes gradually
again with agreements among people.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-03-15 9:28 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
2022-03-15 8:13 ` Jean Louis
2022-03-15 8:36 ` tomas
2022-03-15 9:28 ` Jean Louis [this message]
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=YjBcOXsenpytuuKS@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
--cc=tomas@tuxteam.de \
/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).