From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: Why can't `gnus-draft-setup' be bytecompiled?
Date: 14 Mar 1998 04:23:02 +0100 [thread overview]
Message-ID: <kigzpiu552h.fsf@jagor.srce.hr> (raw)
In-Reply-To: Hallvard B Furuseth's message of "14 Mar 1998 04:11:29 +0100"
Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
> A hack which works in emacs19 as well is to replace (make-symbol "foo")
> with (gensym "foo").
Doesn't that require `cl.el'? Last time I checked, Stallman didn't
want many packages to use the CL extensions.
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Which is worse: ignorance or apathy? Who knows? Who cares?
next prev parent reply other threads:[~1998-03-14 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-03-09 23:01 SL Baur
1998-03-09 23:19 ` Hrvoje Niksic
1998-03-13 21:39 ` Lars Magne Ingebrigtsen
1998-03-14 3:11 ` Hallvard B Furuseth
1998-03-14 3:23 ` Hrvoje Niksic [this message]
1998-03-14 4:09 ` Aaron M. Ucko
1998-03-19 12:30 ` Lars Magne Ingebrigtsen
1998-03-21 2:09 ` Aaron M. Ucko
1998-03-23 13:15 ` Lars Magne Ingebrigtsen
1998-03-14 2:29 ` Hallvard B Furuseth
1998-03-19 12:25 ` Lars Magne Ingebrigtsen
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=kigzpiu552h.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).