From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: nndraft lossage and byte-compilation
Date: 01 Mar 2001 22:27:52 -0500 [thread overview]
Message-ID: <2npug0rgsn.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <y68hf1dhwtt.fsf@alice-whacker.mit.edu> ("David Z. Maze"'s message of "01 Mar 2001 18:51:42 -0500")
"David Z. Maze" <dmaze@MIT.EDU> writes:
> I've run into various random problems with my drafts group; mostly,
> I've been completely unable to access it. This is problematic because
> I'm having other local configuration problems which result in my not
> being able to send mail in some cases; I'd rather be able to save the
> mail than lose it. C-c C-d seems to work, but I can't access the
> draft group at all. I'm pretty sure I've mentioned this both here and
> on gnu.emacs.gnus in the past.
>
> Today, on a whim, I decided to byte-compile my Gnus (couple-day-old
> Oort). And now nndraft works.
>
> The particular thing that prompted me to try this was 'C-h f
> nndraft-request-group'. Now (with the byte-compiled Gnus) it's a
> normal function, but before it was defalias'd to 'ignore. My guess is
> that the (eval-when-compile (defalias ...)) is being evaluated when
> the uncompiled file is loaded, and nnoo-import is failing to override
> that alias with the appropriate nnmh function. When the compiled file
> is loaded, there's no alias, and so calling nnoo-import works. (This
> all makes sense if defaliasing a symbol causes fboundp on it to return
> t.)
Thank you for your report. I've checked in a fix.
ShengHuo
next prev parent reply other threads:[~2001-03-02 3:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 23:51 David Z. Maze
2001-03-02 3:27 ` ShengHuo ZHU [this message]
2001-03-02 13:28 ` Charles Sebold
2001-03-02 18:56 ` ShengHuo ZHU
2001-03-02 19:20 ` Charles Sebold
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=2npug0rgsn.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).