Re: Multiple frame problem

[Reid Rivenburgh <reid@lanl.gov>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1864 bytes --]

 Kai Großjohann writes:

 > Reid Rivenburgh <reid@lanl.gov> writes:
 >> I currently use a setup that pops up a new frame for composing
 >> mail and posts, leaving my original frame for normal reading.

 > It ought to be possible using the normal method of configuring
 > frames and windows and buffers in Gnus.  Alas, I'm not an expert --
 > I just use the default and I'm happy.

 > But I'm sure if you post what configuration you currently use, some
 > buffer configuration guru will be able to tell you how to frob it
 > to get what you want.

Thanks, Kai.  I wasn't sure how much info to include in my previous
message.  I had asked before how to go about getting the separate
frame for compositions, and I believe David Goldberg was kind enough
to post something from his .gnus.el.  Here's what I'm using:

(gnus-add-configuration
 '(message
   (frame 1.0
	  (if (not (buffer-live-p gnus-summary-buffer))
	      (car (cdr (assoc 'group gnus-buffer-configuration)))
	    (car (cdr (assoc 'summary gnus-buffer-configuration))))
	  (vertical (user-position t width 80 top 0 left 0 name "Gnus Edit")
		    (message 1.0 point)))))

The same for reply-yank, reply, and forward.  And as I mentioned in my
previous message, I'm using some hooks to raise and lower the
composition frame as appropriate:

(add-hook 'message-sent-hook (lambda () (bury-buffer (get-buffer
          "*Group*"))) (lower-frame)))
(add-hook 'message-setup-hook (lambda () (raise-frame (next-frame))))

It feels like a mighty big kludge, but it mostly works.  (Sometimes
something in the message-sent-hook outright kills XEmacs, but I
haven't yet diagnosed that one, annoying as it is.)  I'd just like it
to not try to switch to the main gnus buffers (*Group*, *Summary*,
etc.) in the composition frame after sending the message.

Thanks,
Reid