Gnus development mailing list
 help / color / mirror / Atom feed
* Re: Follow-up etc in NEW frame
       [not found]     ` <v93c0khqgk.fsf@marauder.physik.uni-ulm.de>
@ 2004-10-12 15:41       ` Reiner Steib
  2004-10-12 21:15         ` Stefan Monnier
  0 siblings, 1 reply; 2+ messages in thread
From: Reiner Steib @ 2004-10-12 15:41 UTC (permalink / raw)
  Cc: Ding List

[ The following message is a courtesy copy of an article that has
  been posted to news:gnu.emacs.gnus as well. ]

[ Added Cc to the ding list.  If anyone thinks that this patch is not
  the right solution, please speak up.  I'd suggest to contionue the
  thread on the ding list. ]

On Mon, Oct 11 2004, Reiner Steib wrote:

> On Mon, Oct 11 2004, Xavier Maillard wrote:
>> Any chance we can see what does it look like in action (ie. any
>> picture) ?
>
> Both solutions [1] 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):
>
> E.g. when the question "Remove the backup file" from
> `message-kill-buffer' (after `C-c C-k') appears, the frame has already
> been deleted.
[...]
> Thus the message appears in some other (non-focused) frame.  Maybe
> someone has a solution for this problem.

The following patch (already installed in No Gnus) should fix this:

--8<---------------cut here---------------start------------->8---
--- message.el	08 Oct 2004 17:33:21 +0200	7.52
+++ message.el	12 Oct 2004 17:31:14 +0200	
@@ -3417,8 +3417,15 @@
 			  (file-exists-p auto-save-file-name))
 		     (and file-name
 			  (file-exists-p file-name)))
-	       (yes-or-no-p (format "Remove the backup file%s? "
-				    (if modified " too" ""))))
+		 (progn
+		   ;; If the message buffer has lived in a dedicated window,
+		   ;; `kill-buffer' has killed the frame.  Thus the
+		   ;; `yes-or-no-p' may show up in a lowered frame.  Make sure
+		   ;; that the user can see the question by raising the
+		   ;; current frame:
+		   (raise-frame)
+		   (yes-or-no-p (format "Remove the backup file%s? "
+					(if modified " too" "")))))
 	(ignore-errors
 	  (delete-file auto-save-file-name))
 	(let ((message-draft-article draft-article))
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.

[1]
,----[ <news:v9d5zpth1z.fsf@marauder.physik.uni-ulm.de> ]
| On Sun, Oct 10 2004, Simon Kellett wrote:
| 
| > I would like to do my replies/followups/new posts in a new frame 
| 
| In Emacs, you can modify `special-display-regexps' and
| `special-display-buffer-names' (I don't about XEmacs).  You may find
| <URL:http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/rs-special-display.el>
| useful to find out which buffer names to add.
| 
| A different possibility is `gnus-buffer-configuration'.  Katsumi
| Yamaoka has posted his setup for new frames some time ago on ding, see
| <URL:http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/gnus/rs-gnus-win.el>.
| IIRC he has posted an update later.  I don't have the Message-Id for
| it and I didn't include it in `rs-gnus-win.el' because I switched to
| the special display solution.
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Follow-up etc in NEW frame
  2004-10-12 15:41       ` Follow-up etc in NEW frame Reiner Steib
@ 2004-10-12 21:15         ` Stefan Monnier
  0 siblings, 0 replies; 2+ messages in thread
From: Stefan Monnier @ 2004-10-12 21:15 UTC (permalink / raw)
  Cc: Ding List

The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.

> [ Added Cc to the ding list.  If anyone thinks that this patch is not
>   the right solution, please speak up.  I'd suggest to contionue the
>   thread on the ding list. ]

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.

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


        Stefan



^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-10-12 21:15 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <m3sm8mjtyl.fsf@arcor.de>
     [not found] ` <v9d5zpth1z.fsf@marauder.physik.uni-ulm.de>
     [not found]   ` <plop87acutvwh6.fsf@gnu-rox.org>
     [not found]     ` <v93c0khqgk.fsf@marauder.physik.uni-ulm.de>
2004-10-12 15:41       ` Follow-up etc in NEW frame Reiner Steib
2004-10-12 21:15         ` Stefan Monnier

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