From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Window height 3 too small (after splitting)
Date: 02 Dec 1999 13:01:11 +1100 [thread overview]
Message-ID: <t4iemd69k48.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Wed, 01 Dec 1999 21:57:01 +0100"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> `(setq debug-on-error t)', repeat the bug and mail me the resulting
Lars> backtrace.
Hope this helps...
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>)
bbdb/gnus-pop-up-bbdb-buffer(nil)
bbdb/gnus-update-record()
run-hooks(bbdb/gnus-update-record)
apply(run-hooks bbdb/gnus-update-record)
gnus-run-hooks(gnus-article-prepare-hook)
gnus-article-prepare-display()
gnus-article-prepare(253 nil)
gnus-summary-display-article(253 nil)
gnus-summary-select-article(nil nil nil 253)
byte-code("\bqˆ
[-- Attachment #2: Type: text/plain, Size: 2 bytes --]
ÁÂ
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: Type: text/plain, Size: 5 bytes --]
‰‰\v$ˆ
[-- Attachment #4: Type: text/plain, Size: 3 bytes --]
Ä\v!
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #5: Type: text/plain, Size: 1256 bytes --]
‡" [gnus-summary-buffer gnus-summary-select-article nil article gnus-summary-remove-process-mark] 5)
gnus-inews-yank-articles((252 253 254))
gnus-summary-reply((252 253 254) nil)
gnus-summary-reply-with-original(nil)
call-interactively(gnus-summary-reply-with-original)
Normally, when replying, the window is resized, but I am not
sure if this occurs before or after this error.
I suspect this section of my config file may also
be relevant (copied from somewhere, perhaps the Info doc):
(setq gnus-use-trees t
gnus-generate-tree-function 'gnus-generate-horizontal-tree
gnus-tree-minimize-window nil)
(gnus-add-configuration
'(article
(vertical 1.0
(horizontal 0.25
(summary 0.75 point)
(tree 1.0))
(article 1.0))))
PS, when sending this message, I got the following warning:
Warning: Your message contains 5 parts. Really send? (y or n)
5 parts??? That was before I had any MIME attachments.
I said n
then I got the message
Edit your message to use only one charset
So, I will attach another copy of that buffer, in case the first
one doesn't work:
next prev parent reply other threads:[~1999-12-02 2:01 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 [this message]
1999-12-02 2:10 ` Lars Magne Ingebrigtsen
1999-12-02 3:12 ` Brian May
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=t4iemd69k48.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).