Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Cannot enter Summary Buffer with recent Emacs 23 and No Gnus
Date: Mon, 7 Apr 2008 08:15:41 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080407T080800-983@post.gmane.org> (raw)

Hi all,

I use Emacs 23 & No Gnus, both are up-to-date. When I want to enter the Summary
buffer, I get an error signaled and with debug-on-error enabled, I get this
backtrace:

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
...))))
  gnus-configure-windows(summary force)
  gnus-summary-read-group-1("nntp+Gmane:gmane.emacs.gnus.user" nil t nil nil nil)
  gnus-summary-read-group("nntp+Gmane:gmane.emacs.gnus.user" nil t nil nil nil nil)
  gnus-group-read-group(nil t)
  gnus-group-select-group(nil)
  gnus-topic-select-group(nil)
  call-interactively(gnus-topic-select-group nil nil)

This happens with all groups, no matter what backend is used.  Any clue what
might have broken this?

The last time I did a cvs up on Emacs and Gnus was last Friday, so the
problematic change must have been committed in between that time.  A quick look
at the changelogs didn't find anything obvious, though.

Bye,
Tassilo




             reply	other threads:[~2008-04-07  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07  8:15 Tassilo Horn [this message]
2008-04-07  8:27 ` Katsumi Yamaoka
2008-04-07  8:55   ` Tassilo Horn
2008-04-07 11:22     ` Marcus Frings
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=loom.20080407T080800-983@post.gmane.org \
    --to=tassilo@member.fsf.org \
    --cc=ding@gnus.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.
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).