From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org
Subject: Re: DONTCOMPILE in lisp/Makefile.in doesn't work.
Date: Tue, 12 Apr 2005 09:54:20 +0200 [thread overview]
Message-ID: <87sm1wzaz7.fsf@xs4all.nl> (raw)
In-Reply-To: <E1DLBch-0000rn-I9@fencepost.gnu.org> (Richard Stallman's message of "Mon, 11 Apr 2005 22:59:31 -0400")
Richard Stallman <rms@gnu.org> writes:
> Isn't it better to just do away with DONTCOMPILE and just rely on lisp
> files setting no-byte-compile?
>
> I think so. It would be simpler to use just one mechanism,
> and no-byte-compile is cleaner. Could you please do that,
> and put no-byte-compile into any files which could use it and
> don't have it?
I'll do that.
Lute.
next prev parent reply other threads:[~2005-04-12 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 15:15 DONTCOMPILE in lisp/Makefile.in doesn't work Lute Kamstra
2005-04-12 2:59 ` Richard Stallman
2005-04-12 7:54 ` Lute Kamstra [this message]
2005-04-13 10:25 ` Lute Kamstra
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=87sm1wzaz7.fsf@xs4all.nl \
--to=lute.kamstra.lists@xs4all.nl \
--cc=emacs-devel@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.
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).