Gnus development mailing list
 help / color / mirror / Atom feed
From: Reid Rivenburgh <reid@lanl.gov>
Subject: Better handling of reply configuration
Date: 15 Mar 2000 15:05:13 -0700	[thread overview]
Message-ID: <vetwvn3nb3a.fsf@toespaz.c3.lanl.gov> (raw)

One of the few areas where gnus is awkward is the handling of
frames/windows when replying to mail.  I've looked over the gnus
configuration capabilities, but either it doesn't offer quite enough
or I'm too ignorant to use it correctly (yes, probably the latter).  I
also searched in various places and came up basically empty.

The problem is that when replying, the reply buffer takes over the
frame.  If I want to refer back to the original message (if I haven't
yanked it into the reply) or look at a different message, I have to go
through some buffer switching and resizing contortions.

This can be solved by either:

1. Giving the reply its own frame.  This would work fine, but I've had
   a heck of a time getting the frame to go away (delete or iconify)
   when done and having the original frame be unaffected by the reply
   creation.  It would also be nice for general mail composition, not
   just replying.

2. Set up a configuration in a single frame such that the reply takes
   up only a portion of the frame, leaving the summary and article
   buffers visible (but probably reduced in size).  This ought to
   work, too, but there's a question of what happens to the reply
   buffer if I quit the summary to look in another group.  I tried the
   following, but I didn't know how the buffer-live-p split form
   syntax should look (the example in the manual only uses a single
   form after the if).  I think I'm on the right track....

(gnus-add-configuration
 '(reply
   (horizontal 1.0
	       (vertical 20
			 (if (buffer-live-p gnus-message-buffer)
			     '(list (summary .2)
				    (message 1.0 point))
			   '((summary .8 point)
			     (tree 1.0))))
	       (vertical 1.0
			 (article 1.0)))))

I thought I'd throw this out to the list in case anyone has solved the
problem.  Thanks in advance.

Reid



             reply	other threads:[~2000-03-15 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15 22:05 Reid Rivenburgh [this message]
2000-03-15 23:43 ` Kai Großjohann
2000-03-15 23:51   ` Reid Rivenburgh
2000-03-16  0:20     ` Kai Großjohann
2000-03-16 18:03 ` David S. Goldberg
2000-03-16 22:42   ` Reid Rivenburgh

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=vetwvn3nb3a.fsf@toespaz.c3.lanl.gov \
    --to=reid@lanl.gov \
    /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).