Re: Follow-up etc in NEW frame

Re: Follow-up etc in NEW frame

[Reiner Steib]

On Tue, Oct 12 2004, Stefan Monnier wrote:

> Raising the frame just reduces the pain but doesn't eliminate the problem.
> E.g. with multi-workspace window-manager, the frame you're raising
> might not even be visible, so raising it won't help much.

Usually I have all frames of my Gnus session on the same workspace,
but I remember now that I saw this too.  Thanks for pointing this out.

> I think the right solution is to prompt the user before killing the buffer.

The code was:

      (setq buffer-file-name nil)
      (kill-buffer (current-buffer))
      (when [...]
	(ignore-errors
	  (delete-file auto-save-file-name))
	(let ((message-draft-article draft-article))
	  (message-disassociate-draft)))

Do you see any possible problem in moving `kill-buffer' after
`message-disassociate-draft'?

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: Follow-up etc in NEW frame

[Sebastien Kirche]

Hi,

Le 11 Oct 2004, Reiner Steib a formulé :

> Both solutions lead to new frames when composing messages, e.g. when
> pressing `F', `R' and similar, you get a new frame.  When pressing
> `C-c C-c', the frame is closed automatically.
> 
> Alas, there are a couple of minor pitfalls (at least with my
> special-display configuration):

I have another  problem : when i  compose a new message or  reply to another
one, Gnus do create a new frame, but it is not closed at C-c C-c.
The buffer message is actually killed.

I  have a quite  recent Gnus  (from CVS  Emacs) and  did not  find something
usefull in message.el

Do you know a solution ?

Sébastien Kirche