Re: Getting rid of *sent ... buffers

Re: Getting rid of *sent ... buffers

[John Paul Wallington]

Peter Davis wrote:

>  Is there a way to tell gnus/message-mode to
>  automatically close the buffer once the message is sent?

Yup.  See variable `message-kill-buffer-on-exit'.

Re: Getting rid of *sent ... buffers

[Peter Davis]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> See variable message-max-buffers: it won't eat *all* memory.

Thanks, Kai.  Hmmm.  I was hoping this would hoping that setting
message-kill-buffer-on-exit would dramatically reduce the XEmacs/gnus
memory footprint.

Thanks,

-pd


-- 
--------
                             Peter Davis
               Funny stuff at http://www.pfdstudio.com
                 The artwork formerly shown as prints
    List of resources for children's writers and illustrators at:
                  http://www.pfdstudio.com/cwrl.html

Re: Getting rid of *sent ... buffers

[Emerick Rogul]

John Paul Wallington writes:

> Peter Davis wrote:
>> Is there a way to tell gnus/message-mode to
>> automatically close the buffer once the message is sent?

> Yup.  See variable `message-kill-buffer-on-exit'.

Just out of curiosity, is there a reason that
message-kill-buffer-on-exit defaults to nil rather than t?  I can't
understand why you would want to keep a reply buffer around after the
message has been sent, although I'm sure there must be some reason.

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul             /\/     "how young are you, how old am i?
emerick@cs.bu.edu         /\/      let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats