From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: gnus-configure-buffer
Date: 07 Jan 1999 02:43:57 +0100 [thread overview]
Message-ID: <kigogob502q.fsf@jagor.srce.hr> (raw)
In-Reply-To: Anders Melchiorsen's message of "07 Jan 1999 01:14:02 +0100"
Anders Melchiorsen <and@kampsax.dtu.dk> writes:
> I have tried and tried. I am unable to understand the manual on
> Windows Configuration, though.
It's very tough to understand; however, once the light dawns on you,
the window configuration stuff is extremely powerful. Here is what I
use to get a Tree display along with the Summary:
(gnus-add-configuration '(article
(vertical 1.0
(horizontal 0.25
(summary 0.75 point)
(tree 1.0))
(article 1.0))))
> What I would like was for any message-mode buffer to pop up in its
> own frame. When I exit editing the message the frame should close.
Hmm. I am unable to beat Gnus into doing something like this. One
might expect this to pop up a 10x10 frame for messages:
(gnus-add-configuration
'(message (frame (height 10 width 10) (message 1.0))))
However, it stays content with showing the message in the existing
frame. The following does create a new frame, but it doesn't respect
the plist, nor does it remove the new frame when `C-c C-k' is
performed.
(gnus-add-configuration
'(message (frame (height 10 width 10) (message 1.0) (message 1.0))))
Also, with the above, the "old" frame changes to message, which is
wrong.
I am not sure current window-configuration stuff can be made to do
what you want automatically. Lars, could you perhaps extend it to
accomodate this? Is the current behaviour a bug or a feature?
next prev parent reply other threads:[~1999-01-07 1:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-07 0:14 gnus-configure-buffer Anders Melchiorsen
1999-01-07 1:43 ` Hrvoje Niksic [this message]
1999-01-07 17:05 ` gnus-configure-buffer David S. Goldberg
1999-01-08 15:23 ` gnus-configure-buffer Hrvoje Niksic
1999-01-12 7:00 ` gnus-configure-buffer Lars Magne Ingebrigtsen
1999-01-12 18:19 ` gnus-configure-buffer David S. Goldberg
1999-01-08 21:02 ` gnus-configure-buffer Jack Vinson
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=kigogob502q.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/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).