Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Window height 3 too small (after splitting)
Date: 02 Dec 1999 14:12:38 +1100	[thread overview]
Message-ID: <t4iemd6vxw9.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Thu, 02 Dec 1999 03:10:48 +0100"

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

    Lars> Brian May <bmay@csse.monash.edu.au> writes:
    >> Signaling: (error "Window height 3 too small (after
    >> splitting)") split-window(#<window on "*reply to Brian May*"
    >> 0x857d> 3) bbdb-pop-up-bbdb-buffer(#<compiled-function (from
    >> "bbdb-gnus.elc") (w) "...(28)" [b window-buffer w major-mode
    >> gnus-Article-mode gnus-article-mode] 2>)

    Lars> So this seems like a bbdb-related bug.

I was more inclined to think it was supercite, AFAIK bbdb shouldn't be
doing anything at the time. While supercite has a feature to use bbdb
for citations, I haven't yet worked out how to enable it.

Of course, I might be totally lost.

    >> PS, when sending this message, I got the following warning:
    >> 
    >> Warning: Your message contains 5 parts.  Really send? (y or n)

    Lars> The binary junk in the backtrace made XEmacs think that
    Lars> there was lots of weird characters there.  Hm.

Not only that, but my attachment at the bottom of the message
was truncated (and subsequent text).

I thought this might happen, it didn't show up in preview mode,
either.
-- 
Brian May <bmay@csse.monash.edu.au>


  reply	other threads:[~1999-12-02  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-25  5:27 Brian May
1999-12-01 20:57 ` Lars Magne Ingebrigtsen
1999-12-02  2:01   ` Brian May
1999-12-02  2:10     ` Lars Magne Ingebrigtsen
1999-12-02  3:12       ` Brian May [this message]
1999-12-02  3:27         ` 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=t4iemd6vxw9.fsf@silas-2.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).