From: Marcus Frings <iam-est-hora-surgere@despammed.com>
To: ding@gnus.org
Subject: Re: Cannot enter Summary Buffer with recent Emacs 23 and No Gnus
Date: Mon, 07 Apr 2008 13:22:24 +0200 [thread overview]
Message-ID: <vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87myo5ewpb.fsf@shodan.gothgoose.net> (raw)
In-Reply-To: <87ej9iyrfk.fsf@member.fsf.org>
* Tassilo Horn <tassilo@member.fsf.org> wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>> Debugger entered--Lisp error: (error "Invalid size: gnus-carpal")
>>> signal(error ("Invalid size: gnus-carpal"))
>>> error("Invalid size: %s" gnus-carpal)
>>> gnus-configure-frame((vertical 1.0 (summary 1.0 point) (if gnus-carpal (quote
>> Doesn't this do the trick?
>> (or (functionp 'if)
>> (defadvice functionp (around workaround-bug (object) activate)
>> "Workaround bug."
>> (or ad-do-it
>> (setq ad-return-value (and (symbolp object) (fboundp object))))))
> Indeed. Befare evaling this, (functionp 'if) return nil. After
> evaluation, it's t again and gnus works as it should.
I can confirm this. I'm using an up-to-date CVS Gnus and the latest
emacs-snapshot package from <URL:http://emacs.orebokech.com/> on
Debian. Your workaround fixes this problem. Has anyone already reported
this to the Emacs developers?
Regards,
Marcus
--
"Tracer cartridges are used for target indication, fire adjustment, signal
purposes and destroying personnel. Tracer bullets can ignite. The path of the
bullet is indicated by a red flame. AP incendiary cartridges are used for
destroying fuel, gasoline and for destroying targets protected by thin armour."
next prev parent reply other threads:[~2008-04-07 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 8:15 Tassilo Horn
2008-04-07 8:27 ` Katsumi Yamaoka
2008-04-07 8:55 ` Tassilo Horn
2008-04-07 11:22 ` Marcus Frings [this message]
2008-04-08 6:39 ` Tassilo Horn
2008-04-08 11:33 ` Marcus Frings
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=vita-brevis-breviter-in-brevi-finietur-mors-venit-velociter-quae-neminem-veretur-87myo5ewpb.fsf@shodan.gothgoose.net \
--to=iam-est-hora-surgere@despammed.com \
--cc=ding@gnus.org \
--cc=protagonist@gmx.net \
/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).