From: Karl Kleinpaste <karl@lycos.com>
Subject: gnus-buffer-configuration
Date: Thu, 27 Jun 1996 13:42:17 -0400 [thread overview]
Message-ID: <199606271742.NAA24373@gorilla.eng.lycos.com> (raw)
5.2.25 as supplied with xemacs 19.14.
There is a redundant usage of gnus-use-trees in
gnus-buffer-configuration, in the default `t' case. There's already a
gnus-use-trees entry under the cond; it's pointless under the `t'.
Much more generally...I am catching up -- 'waaaay up -- from
5.0.something to 5.2.25 now, and I'm finding gnus-buffer-configuration
completely incomprehensible. Of importance to me, I used to work with
a configuration like this, using a really wide (168-column) emacs:
---------------------
| Group | | This used to be accomplished with
|---------| | (gnus-add-configuration
| | Article | '(article ((group 0.25)
| Summary | | (summary 1.0 point))
| | | ((horizontal 0.5)
| | | (article 1.0))))
---------------------
I have a number of (horizontal 0.5) entries, and depend on it pretty
heavily (mail-forward and edit-group are very similar). The *Info*
documentation on gnus-buffer-configuration is really out of date, in
that it doesn't reference (e.g.) "vertical" as a g-b-c element at all,
even though it's all over the default g-b-c setting in gnus.el.
Could someone provide a clue? I feel like I'm missing something large
but obvious here. There are no horizontal examples from which to work
anywhere at this point.
next reply other threads:[~1996-06-27 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-27 17:42 Karl Kleinpaste [this message]
1996-06-27 19:33 ` gnus-buffer-configuration Lars Magne Ingebrigtsen
1996-06-27 21:05 ` gnus-buffer-configuration Karl Kleinpaste
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=199606271742.NAA24373@gorilla.eng.lycos.com \
--to=karl@lycos.com \
/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).