unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: Is there a way of setting a variable only when it exists?
Date: Fri, 18 Mar 2022 20:59:47 +0300	[thread overview]
Message-ID: <YjTIk4Wklbt8VdAA@protected.localdomain> (raw)
In-Reply-To: <87tubxbpq7.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2022-03-17 21:59]:
> Marcin Borkowski wrote:
> 
> >> If that happens, compiling your init.el will then normally
> >> give you an "assignment to free variable" warning, no?
> >
> > I didn't think about it. OTOH, why would I compile my
> > init.el?
> 
> To get .elc which is better, faster byte-code as well as the
> other advantages of code-improvement that the byte-compiler's
> messages leads to if you take proper action ...
> 
> This has been mentioned many times over the years here not the
> least ...

It's going to be over the years not easily understood. Maybe Emacs
need some better "warning" or instructions how to initiate byte
compiling.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2022-03-18 17:59 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
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 [this message]
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=YjTIk4Wklbt8VdAA@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /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).