From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Compiled format specs in .newsrc.eld?
Date: Sun, 16 Jun 2002 04:23:17 +0200 [thread overview]
Message-ID: <m3znxwklm2.fsf@defun.localdomain> (raw)
In-Reply-To: <vaffzzo1lz3.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 15 Jun 2002 17:39:48 +0000 (UTC)")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Jesper Harder <harder@ifa.au.dk> writes:
>
>> But when I look in my .newsrc.eld, I don't see any trace of byte-code.
>> Is it a bug?
>
> gnus-compile compiles from a string to Lisp code. Byte-compiling the
> Lisp code would be another step, which is not implemented.
Hmm, are you sure? The doc-string for `gnus-compile' is
"Byte-compile the user-defined format specs."
and when I look at the function that seems to be exactly what it does.
I think `gnus-update-format-specifications' is the defun responsible for
converting format strings to Lisp.
But in any case, neither the non-compiled Lisp versions nor the
byte-compiled versions are saved in my .newsrc.eld.
next prev parent reply other threads:[~2002-06-16 2:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 0:35 Jesper Harder
2002-06-15 10:00 ` Simon Josefsson
2002-06-15 16:15 ` Jesper Harder
2002-06-15 17:38 ` Kai Großjohann
2002-06-16 2:23 ` Jesper Harder [this message]
2002-06-16 10:04 ` Kai Großjohann
2002-06-17 12:13 ` Katsumi Yamaoka
2002-06-17 13:31 ` Kai Großjohann
2002-06-17 14:03 ` Jesper Harder
2002-06-17 14:03 ` Simon Josefsson
2002-06-17 14:09 ` Jesper Harder
2002-06-17 14:17 ` Simon Josefsson
2002-06-17 15:13 ` Jesper Harder
2002-06-17 15:56 ` Simon Josefsson
2002-06-17 16:31 ` Jesper Harder
2002-06-17 16:54 ` Simon Josefsson
2002-06-17 19:59 ` Jesper Harder
2002-06-17 16:25 ` Kai Großjohann
2002-06-17 15:36 ` Kai Großjohann
2002-06-17 23:13 ` Katsumi Yamaoka
2002-06-18 2:12 ` Katsumi Yamaoka
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3znxwklm2.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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 NNTP newsgroup(s).