unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: era@iki.fi
Subject: Re: Bug in emacs
Date: 13 Oct 2003 15:39:07 +0300	[thread overview]
Message-ID: <871xthmi70.fsf@era.iki.fi> (raw)
In-Reply-To: 004301c38cd9$2260b1a0$0100a8c0@athlon

On Tue, 7 Oct 2003 15:44:30 +0200, Jean Pierre Lemue
<jp-lemue@club-internet.fr> posted to gmane.emacs.bugs:
 > I have a big bug on emacs. I can't resolve it.

If you have macros which influence the meaning of forms you are
compiling, the macro needs to be loaded before you compile. What you
are reporting seems like a typical symptom of failing to load the
macro in question before compiling.

A workaround would be to make sure you eval the macro definition
before compiling.

I'm not sure what the bug really is. Perhaps it would be useful to get
a warning when compiling / evaling something when a macro +is+ in
effect and the file you are compiling is not pulling it in properly?
Then at least you get a hint to fix it while you still can, while
those who do it right will not experience any adverse effects.

/* era */

-- 
The email address era     the contact information   Just for kicks, imagine
at iki dot fi is heavily  link on my home page at   what it's like to get
spam filtered.  If you    <http://www.iki.fi/era/>  500 pieces of spam for
want to reach me, see     instead.                  each wanted message.

  reply	other threads:[~2003-10-13 12:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07 13:44 Bug in emacs Jean Pierre Lemue
2003-10-13 12:39 ` era [this message]
     [not found] ` <mailman.1587.1066050220.21628.bug-gnu-emacs@gnu.org>
2003-10-13 16:28   ` Kevin Rodgers
2003-10-14  6:05     ` era
2003-10-16  7:59       ` era
2003-10-17  8:52         ` era
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05  0:25 Eric J Russell
2005-10-05 22:45 ` Richard M. Stallman

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=871xthmi70.fsf@era.iki.fi \
    --to=era@iki.fi \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).