Gnus development mailing list
 help / color / mirror / Atom feed
From: dsg@mitre.org (David S. Goldberg)
Subject: Re: Better handling of reply configuration
Date: 16 Mar 2000 13:03:57 -0500	[thread overview]
Message-ID: <m1b66umg5bm.fsf@blackbird.mitre.org> (raw)
In-Reply-To: <vetwvn3nb3a.fsf@toespaz.c3.lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

> 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.

No, you're right.  It is awkward.  This has come up before on the
mailing list but there's no real satisfying solution.  As you've
already worked out with Kai, the defaults (in a single frame) are
pretty reasonable.

> 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.

It gets really weird when you want to have your message buffer in a
different frame.  I use the following which works quite well, but I
feel like I shouldn't have had to do so much work to get it that way.

I use a large window dedicated to Gnus.  I put my group, article and
summary configs here for illustration 


[-- Attachment #2: Type: application/emacs-lisp, Size: 478 bytes --]

[-- Attachment #3: Type: text/plain, Size: 319 bytes --]


This is my message config.  The trick is to get the message
composition buffer in a separate frame while leaving the original
frame intact.  There should be a better way.  I started to hack at
something back in early pgnus days but didn't have time to do it
justice.  When ognus gets going, I hope to get back to it.


[-- Attachment #4: Type: application/emacs-lisp, Size: 367 bytes --]

[-- Attachment #5: Type: text/plain, Size: 848 bytes --]


First ignore the name in the frame params.  I use that to get fvwm2 to
give the window a specific icon in my fvwm2 icon manager.  The key is
the if statement.  The message config is used when you do an m in
either the group or summary buffers to generate a new mail.  So if
there's a live summary buffer, I assume I'm in summary mode and I
enforce the summary configuration in the main frame and put the
message buffer in a new one.  If there's no summary, I enforce the
group configuration on the main frame.  Similar for the post
configuration.  For reply, reply-yank, forward and draft I do
essentially the same thing except there's no need to check for summary
mode.  In those cases I force article configuration (except for draft
which is summary) on the main frame and put the message in the new
frame.  Here's reply-yank to illustrate it.


[-- Attachment #6: Type: application/emacs-lisp, Size: 259 bytes --]

[-- Attachment #7: Type: text/plain, Size: 436 bytes --]


I don't remove the message frame after sending.  I write a lot of
email and find that the time spent rebuilding new frames is a
waste.  However, I believe you can use message-sent-hook to either
delete or iconfiy the frame.  Just make sure to select the right
frame for deleting or iconifying :-)

hth,
-- 
Dave Goldberg
Post: The Mitre Corporation\MS B325\202 Burlington Rd.\Bedford, MA 01730
Phone: 781-271-3887
Email: dsg@mitre.org

  parent reply	other threads:[~2000-03-16 18:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-15 22:05 Reid Rivenburgh
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 [this message]
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=m1b66umg5bm.fsf@blackbird.mitre.org \
    --to=dsg@mitre.org \
    /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).