Re: Follow-up etc in NEW frame

[Reiner Steib <reinersteib+from-uce@imap.cc>]

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/