Gnus development mailing list
 help / color / mirror / Atom feed
From: Kaspar Landsberg <kl@kl.Snafu.DE>
Subject: Re: "Window height 0 too small (after splitting)"
Date: Tue, 19 Oct 1999 15:11:54 +0200	[thread overview]
Message-ID: <19991019151154.A1058@kl.lk.etc.tu-bs.de> (raw)
In-Reply-To: =?iso-8859-1?Q?=3Cvafln90y937=2Efsf=40lucy=2Ecs=2Euni-dortmund=2Ede=3E?= =?iso-8859-1?Q?=3B_from_Kai_Gro=DFjohann_on_Mon=2C_Oct_18=2C_1999_at_05:?= =?iso-8859-1?Q?36:28PM_+0200?=

Hi,

On Mon, Oct 18, 1999 at 05:36:28PM +0200, Kai Großjohann wrote:

| I think a minimal aquaintance with Emacs and Lisp is necessary for
| using alpha/development software.  Do you really, really, _really_
| want to use development versions if you don't know what to do when a
| bug crops up?  

Well, yes.

a) because i need the new features in the devel version
b) because i probably won't find any bugs in the production version so
   there is no good way to learn how to deal with bugs other than using a
   devel version :)

| Apropos is your friend.  Search for "gnus.*version" or
| "version.*gnus" for useful functions and variables.  M-x apropos RET
| is not the same as C-h a.

Tried apropos but apparently i didnt feed it correctly. Well, now i found
the right command. Thanks. :)

Btw, coming back to the original problem: It is apparently only related to
pgnus-0.97 because everything works fine with Gnus v5.5.

If, in order to fix that problem, further information is needed, i will
happily try to produce it.

Bye, Kasi

-- 
Kaspar Landsberg, <kl@kl.Snafu.DE>


  reply	other threads:[~1999-10-19 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-18 14:21 Kaspar Landsberg
1999-10-18 15:36 ` Kai Großjohann
1999-10-19 13:11   ` Kaspar Landsberg [this message]
1999-10-19 13:59     ` Kai Großjohann
1999-10-19 19:41       ` Kaspar Landsberg
1999-10-20  2:30 ` Dan Christensen
1999-10-20 17:26   ` Kaspar Landsberg

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=19991019151154.A1058@kl.lk.etc.tu-bs.de \
    --to=kl@kl.snafu.de \
    /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).