unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: steve-humphreys@gmx.com
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: rx expressions
Date: Mon, 1 Feb 2021 13:19:18 +0100	[thread overview]
Message-ID: <trinity-6f0c0083-7ac1-4d69-aedb-ebbd5a94b8ce-1612181958730@3c-app-mailcom-bs14> (raw)
In-Reply-To: <87lfc8f0p0.fsf@zoho.eu>

It is part of a minor mode I have written, and included the following
code.  What do you think?

(eval-when-compile
  (setq byte-compile-function-environment
        (delq (assq 'crucible-mode byte-compile-function-environment)
              byte-compile-function-environment)))



> Sent: Tuesday, February 02, 2021 at 12:10 AM
> From: "moasenwood--- via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: rx expressions
>
> Philip K. wrote:
> 
> >> (eval-when-compile (require 'rx))
> >> (rx--empty)
> >>
> >> geh.el: 
> >> In end of data:
> >> geh.el:294:1: Warning: the function ‘rx--empty’ might not be defined at
> >>     runtime.
> >
> > rx--empty is a function, so it doesn't make sense. I do
> > eval-when-compile when all I use is the rx macro itself.
> 
> Byte-compiling Elisp almost always makes sense, for
> several reasons.
> 
> Use
> 
>   (require 'rx)
> 
> so everything is solid from the get-go and you can focus on
> the byte-compiler messages that are actually useful, even
> interesting to read...
> 
> -- 
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
> 
> 
>



      reply	other threads:[~2021-02-01 12:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31 15:00 rx expressions steve-humphreys
2021-01-31 16:42 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-01-31 18:26 ` Michael Heerdegen
2021-01-31 18:32   ` steve-humphreys
2021-01-31 18:53     ` Michael Heerdegen
2021-02-01  9:49 ` Philip K.
2021-02-01 10:01   ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-01 11:27     ` Philip K.
2021-02-01 12:10       ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-01 12:19         ` steve-humphreys [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=trinity-6f0c0083-7ac1-4d69-aedb-ebbd5a94b8ce-1612181958730@3c-app-mailcom-bs14 \
    --to=steve-humphreys@gmx.com \
    --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).