From: Kevin Falcone <kevinfal@seas.upenn.edu>
Subject: gnus-win breakage
Date: 04 Dec 2000 22:30:35 -0500 [thread overview]
Message-ID: <m3zoibpmsk.fsf@bowline.jibsheet.com> (raw)
I just updated my cvs checkout, and now some of my .gnus code breaks
badly. I have it set up to create a second frame for me to compose
mail in. debug-on-error yields the following.
A copy of my .gnus is available here <http://jibsheet.com/dotgnus>
the code triggering this is at the top of the file.
thanks
-kevin
Signaling: (wrong-type-argument window-live-p nil)
window-frame(nil)
gnus-configure-frame((frame 1.0 (if (not ...) (car ...) (car ...)) (vertical (user-position t top 1 left 1 name "Gnus Edit" buffer-predicate dsg-gnus-buffer-predicate) (message 1.0 point))))
gnus-configure-windows(message t)
gnus-post-news(post "nnml:lists.gnus")
gnus-summary-post-news()
* call-interactively(gnus-summary-post-news)
recursive-edit()
byte-code("Æ\b!ˆÇ\x11È ˆÉÇ!ˆpÊË\x1a^[\x1cÌ ˆ+ebˆÍ ˆ`ÎÏ!ˆÐyˆ`|ˆÑ ˆ\r@Ò>ƒN
debug(error (wrong-type-argument window-live-p nil))
window-frame(nil)
gnus-configure-frame((frame 1.0 (car (cdr ...)) (vertical (user-position t top 1 left 1 name "Gnus Edit" buffer-predicate dsg-gnus-buffer-predicate) (message 1.0 point))))
gnus-configure-windows(reply-yank t)
gnus-summary-reply((5578) nil)
gnus-summary-reply-with-original(nil)
* call-interactively(gnus-summary-reply-with-original)
--
bletch before baz, except after frob.
-- Malcolm Ray
next reply other threads:[~2000-12-05 3:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-05 3:30 Kevin Falcone [this message]
2000-12-05 3:48 ` ShengHuo ZHU
2000-12-05 5:06 ` Kevin Falcone
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=m3zoibpmsk.fsf@bowline.jibsheet.com \
--to=kevinfal@seas.upenn.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).