From: Fabrice Popineau <popineau@esemetz.ese-metz.fr>
Subject: sgnus-0.7x and xemacs 19.13
Date: 29 Apr 1996 11:57:19 +0200 [thread overview]
Message-ID: <wyg29nmjy7.fsf@neuromancer.ese-metz.fr> (raw)
Hi,
I can't use sgnus anymore within xemacs. When I'm in the Summary
buffer, I get "window is not tall enough to split" error message.
I trace the bug (?) downto gnus-configure-frame. When this function is
called, the current window is on the *nntpd* buffer. It appears that
split-window is then called (with the default
gnus-buffer-configuration) with this window and 0 lines as argument.
Unfortunately, xemacs-19.13 can't split windows if the resulting
window has less than 2 lines.
Am I the only one to observe this ?
Thanks,
--
Fabrice POPINEAU
------------------------
e-mail: popineau@ese-metz.fr voice-mail: (+33) 87-74-99-38
surface-mail: Supelec, 2 rue E. Belin, F-57078 Metz Cedex 3
next reply other threads:[~1996-04-29 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-29 9:57 Fabrice Popineau [this message]
[not found] ` <x668ajgff2.fsf@eyesore.no>
1996-04-30 8:06 ` Fabrice Popineau
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=wyg29nmjy7.fsf@neuromancer.ese-metz.fr \
--to=popineau@esemetz.ese-metz.fr \
/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).