unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: weird byte compile message when using (when t ... )
Date: Fri, 12 Feb 2021 15:35:46 +0100	[thread overview]
Message-ID: <877dnduzel.fsf@zoho.eu> (raw)
In-Reply-To: jwvk0rdfl2g.fsf-monnier+emacs@gnu.org

Stefan Monnier wrote:

> The byte-compiler treats code differently if it's
> a "toplevel" or not (where "toplevel" either literally means
> "not nested inside anything else" or "nested inside
> a `progn` (or something that expands to one) that is
> a toplevel").

OK, king, thanks :)

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




      reply	other threads:[~2021-02-12 14:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 13:12 weird byte compile message when using (when t ... ) Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-12 14:17 ` Stefan Monnier
2021-02-12 14:35   ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]

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=877dnduzel.fsf@zoho.eu \
    --to=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).