multiple message frames

multiple message frames

[Katsumi Yamaoka]

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

Hi,

This is my gnus-buffer-configuration.  It makes it possible to
open multiple message frames and delete each frame automatically
after sending it.


[-- Attachment #2: Type: application/emacs-lisp, Size: 1216 bytes --]

[-- Attachment #3: Type: text/plain, Size: 46 bytes --]


Enjoy,
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: multiple message frames

[Jinhyok Heo]

>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:

    KY> Hi,

    KY> This is my gnus-buffer-configuration.  It makes it possible to
    KY> open multiple message frames and delete each frame
    KY> automatically after sending it.

This is the best gnus-buffer-configuration I've seen so far. :)
Thanks a lot.

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk

Re: multiple message frames

[Reiner Steib]

On Fri, Aug 02 2002, Katsumi Yamaoka wrote:

> This is my gnus-buffer-configuration.  It makes it possible to
> open multiple message frames and delete each frame automatically
> after sending it.

Thanks. I really like it. 

Is it possible to kill the frame on `C-c C-d' (message-dont-send) too?

[...]
> (add-hook
>  'gnus-configure-windows-hook
[...]
> 	 (setq message-send-actions
> 	       (nconc message-send-actions
> 		      `((funcall ,delete-frame-function))))

I tried to add ...

	   (setq message-postpone-actions
		 (nconc message-postpone-actions
			`((funcall ,delete-frame-function))))

... here, but the frame isn't killed after `C-c C-d', although the
variable `message-postpone-actions' is changed:

,----[ C-h v message-postpone-actions RET ]
| message-postpone-actions's value is shown below.
| 
| A list of actions to be performed after postponing a message.
| 
| Defined in `message'.
| 
| Value:
| ((set-window-configuration #<window-configuration>)
|  (funcall
|   (lambda nil
|     (if
| 	(and
| 	 (eq
| 	  (selected-window)
| 	  (next-window))
| 	 (eq
| 	  (selected-frame)
| 	  #<frame  *Minibuf-2* 0x882f340>))
| 	(delete-frame #<frame  *Minibuf-2* 0x882f340>)))))
| 
| Local in buffer *wide reply to Katsumi Yamaoka on ding@gnus.org*;
| global value is nil
`----

Any hints?

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

Re: multiple message frames

[Katsumi Yamaoka]

Hi,

Sorry for the late answer.  I came back from the summer vacation.

>>>>> In <v9hei65rz7.fsf@marauder.physik.uni-ulm.de> 
>>>>>	Reiner Steib <4uce.02.r.steib@gmx.net> wrote:

>> This is my gnus-buffer-configuration.  It makes it possible to
>> open multiple message frames and delete each frame automatically
>> after sending it.

> Thanks. I really like it.

Thank you.

> Is it possible to kill the frame on `C-c C-d' (message-dont-send) too?

[...]

> I tried to add ...

> 	   (setq message-postpone-actions
> 		 (nconc message-postpone-actions
> 			`((funcall ,delete-frame-function))))

> ... here, but the frame isn't killed after `C-c C-d', although the
> variable `message-postpone-actions' is changed:

> ,----[ C-h v message-postpone-actions RET ]
> | message-postpone-actions's value is shown below.
> | 
> | A list of actions to be performed after postponing a message.
> | 
> | Defined in `message'.
> | 
> | Value:
> | ((set-window-configuration #<window-configuration>)
> |  (funcall
> |   (lambda nil

[...]

The first element of the actions seems to be needless for the
detached message frame.  It is for restoring the window
configuration for a group buffer or summary+article buffers.
So, we can simply write a code as follows:

	 (setq message-postpone-actions
	       `((funcall ,delete-frame-function)))
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: multiple message frames

[Reiner Steib]

On Mon, Aug 12 2002, Katsumi Yamaoka wrote:

[...]
> 	 (setq message-postpone-actions
> 	       `((funcall ,delete-frame-function)))

Thanks, it works fine now!

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

Re: multiple message frames

[Katsumi Yamaoka]

[-- Attachment #1: Type: text/plain, Size: 388 bytes --]

Hi,

Here's an improved version.  I noticed that I should use
`message-exit-actions' rather than `message-send-actions'
for deleting a message frame.

>>>>> In <yotlznw5h8hy.fsf@jpl.org>
>>>>>	Katsumi Yamaoka <yamaoka@jpl.org> wrote:

> This is my gnus-buffer-configuration.  It makes it possible to
> open multiple message frames and delete each frame automatically
> after sending it.


[-- Attachment #2: Type: application/emacs-lisp, Size: 1231 bytes --]

frames more (Re: multiple message frames)

[Katsumi Yamaoka]

Hi,

I've improved the command `gnus-other-frame' in CVS.
It searches for the existing Gnus frame, it doesn't read new
news if Gnus is already alive, it deletes the frame on exit.
This can be a toolbar item, the following code will work for
both FSF Emacs 21 and XEmacs.

(cond ((featurep 'xemacs)
       (setq toolbar-news-reader 'gnus)
       (setcdr (assq 'gnus toolbar-news-commands-alist) 'gnus-other-frame)
       (setq gnus-other-frame-parameters '(width 80 height 48)))
      ((fboundp 'tool-bar-add-item) ;; Emacs 21.
       (tool-bar-add-item "gnus-pointer" 'gnus-other-frame 'Gnus)
       (setq gnus-other-frame-parameters '((width . 80) (height . 48)))))

If you have any trouble with this change, please let me know.
I will fix the problems as soon as possible.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: frames more (Re: multiple message frames)

[Jinhyok Heo]

I've found some problems.

I use gnuclient from time to time when I work on another X window. If
I running a xemacs on one window and I try gnuclient on the other, a
new frame is made in a wrong way.

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk

Re: frames more (Re: multiple message frames)

[Katsumi Yamaoka]

Hi,

>>>>> In <microsoft-free.3o3ct6ytux.fsf@ournature.org> 
>>>>>	Jinhyok Heo <novembre+dated+1030515666.a652c2@ournature.org> wrote:

> I've found some problems.

> I use gnuclient from time to time when I work on another X window. If
> I running a xemacs on one window and I try gnuclient on the other, a
> new frame is made in a wrong way.

Well, there is a non-Gnus frame on the display A, and there is
an iconified Gnus frame on the display B.  If a user clicks the
news toolbar (or types M-x gnus-other-frame) on the display A, a
Gnus frame will be popped up on the display B.  I think it is a
correct behavior.  Isn't it?  Otherwise, do you anticipate that
a Gnus frame is popped up on the display A even if it exists on
the display B?

I'm using (make-frame-on-display "B:0.0") on the display A.
Since I've no experience of using gnuclient, could you please
show me how do you use it?

Regards,
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: frames more (Re: multiple message frames)

[Katsumi Yamaoka]

[-- Attachment #1: Type: text/plain, Size: 579 bytes --]

I've changed my mind. :)

>>>>> In <yotlr8gqqapy.fsf@jpl.org>
>>>>>	Katsumi Yamaoka <yamaoka@jpl.org> wrote:

> Well, there is a non-Gnus frame on the display A, and there is
> an iconified Gnus frame on the display B.  If a user clicks the
> news toolbar (or types M-x gnus-other-frame) on the display A, a
> Gnus frame will be popped up on the display B.  I think it is a
> correct behavior.

No, it's not correct.  That behavior is quite inconvenient if
the display B is away from the display A.  Here's a new one.
Jinhyok, could you please check it whether you are pleased?


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 2686 bytes --]

--- gnus-util.el~	2002-08-21 12:49:51 +0000
+++ gnus-util.el	2002-08-23 10:01:33 +0000
@@ -1287,6 +1287,16 @@
 	 (when focus-follows-mouse
 	   (set-mouse-position frame (1- (frame-width frame)) 0)))))
 
+(defun gnus-frame-or-window-display-name (object)
+  "Given a frame or window, return the associated display name.
+Return nil otherwise."
+  (if (featurep 'xemacs)
+      (device-name (dfw-device object))
+    (if (or (framep object)
+	    (and (windowp object)
+		 (setq object (window-frame object))))
+	(frame-parameter object 'display))))
+
 (provide 'gnus-util)
 
 ;;; gnus-util.el ends here
--- gnus.el~	2002-08-21 23:47:05 +0000
+++ gnus.el	2002-08-23 10:01:33 +0000
@@ -3378,19 +3378,24 @@
 (defun gnus-other-frame (&optional arg)
   "Pop up a frame to read news."
   (interactive "P")
-  (let ((alive (gnus-alive-p)))
-    (unless (and alive
-		 (catch 'found
-		   (walk-windows
-		    (lambda (window)
-		      (when (with-current-buffer (window-buffer window)
-			      (string-match "\\`gnus-.+-mode\\'"
-					    (symbol-name major-mode)))
-			(gnus-select-frame-set-input-focus
-			 (setq gnus-other-frame-object (window-frame window)))
-			(select-window window)
-			(throw 'found t)))
-		    'ignore t)))
+  (let ((alive (gnus-alive-p))
+	(display (gnus-frame-or-window-display-name (selected-frame))))
+    (unless
+	(and
+	 alive
+	 (catch 'found
+	   (walk-windows
+	    (lambda (window)
+	      (when (and (equal display
+				(gnus-frame-or-window-display-name window))
+			 (with-current-buffer (window-buffer window)
+			   (string-match "\\`gnus-.+-mode\\'"
+					 (symbol-name major-mode))))
+		(gnus-select-frame-set-input-focus
+		 (setq gnus-other-frame-object (window-frame window)))
+		(select-window window)
+		(throw 'found t)))
+	    'ignore t)))
       (gnus-select-frame-set-input-focus
        (setq gnus-other-frame-object
 	     (make-frame gnus-other-frame-parameters)))
--- lpath.el~	2002-08-21 12:49:51 +0000
+++ lpath.el	2002-08-23 10:01:33 +0000
@@ -92,7 +92,7 @@
 		     window-edges x-color-values x-popup-menu browse-url
 		     frame-char-height frame-char-width
 		     url-generic-parse-url xml-parse-region
-		     make-network-process))
+		     make-network-process frame-parameter))
       (maybe-bind '(buffer-display-table
 		    buffer-file-coding-system font-lock-defaults
 		    global-face-data gnus-article-x-face-too-ugly
@@ -123,7 +123,8 @@
 		 specifier-instance url-generic-parse-url
 		 valid-image-instantiator-format-p w3-do-setup
 		 window-pixel-height window-pixel-width
-		 xml-parse-region make-network-process)))
+		 xml-parse-region make-network-process
+		 device-name dfw-device)))
 
 (require 'custom)
 

Re: frames more (Re: multiple message frames)

[Jinhyok Heo]

>>>>> "KY" == Katsumi Yamaoka <yamaoka@jpl.org> writes:

    KY> I've changed my mind. :)

Thanks. :)

    KY> No, it's not correct.  That behavior is quite inconvenient if
    KY> the display B is away from the display A.  Here's a new one.
    KY> Jinhyok, could you please check it whether you are pleased?

It doesn't seem to be perfect yet.

I ran xemacs on display A. At the first time on display B, it
worked. But if I tried it again on display A, it didn't work
correctly.

I think you can also check it if you run an another X on your
machine(by doing like "startx -- :2"). Sorry that I'm away this
weekend and I can't test any more until next week.

-- 
| Jinhyok Heo (novembre @ ournature.org || http://ournature.org/~novembre/)
|--------------------------------------------------------------------------
| "We are still reaching for the sky. In the developed countries people
|  are coming back down, saying, `It's empty up there.'" --- a Ladakhi monk

Re: frames more (Re: multiple message frames)

[Katsumi Yamaoka]

>>>>> In <microsoft-free.3optw9u9gm.fsf@ournature.org>
>>>>>	Jinhyok Heo <novembre+dated+1030531782.fdef48@ournature.org> wrote:

> It doesn't seem to be perfect yet.

Thank you for the fast response.

> I ran xemacs on display A. At the first time on display B, it
> worked. But if I tried it again on display A, it didn't work
> correctly.

> I think you can also check it if you run an another X on your
> machine(by doing like "startx -- :2"). Sorry that I'm away this
> weekend and I can't test any more until next week.

I'm now in the office, there are many X machines and I learned
how to use gnuclient.  So, I'll do many trials and errors from
now on.  See you next week.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: frames more (Re: multiple message frames)

[Katsumi Yamaoka]

Hi,

I've CVS committed the 2nd trial of `gnus-other-frame'.  This
can be called by the gnuclient program.  For instance, if you
want to pop up a Gnus frame on the local display, you could say:

  gnuclient -batch -f gnus-other-frame

To pop up a Gnus frame on the remote display "remote:0.0", say:

  gnuclient -batch -eval '(gnus-other-frame nil "remote:0.0")'

Unfortunately, as far as I know, the `-batch' option is needed
to prevent creating of a useless frame, and the `-display'
option will be ignored in such cases.

I've tested it shortly for both FSF Emacs and XEmacs.  I've
downloaded the gnuclient program for FSF Emacs from:

http://meltin.net/hacks/emacs/src/gnuserv-3.12.4.tar.gz
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: multiple message frames

[Reiner Steib]

On Mon, Aug 19 2002, Katsumi Yamaoka wrote:

> Here's an improved version.  I noticed that I should use
> `message-exit-actions' rather than `message-send-actions'
> for deleting a message frame.
[...]
>> This is my gnus-buffer-configuration.  It makes it possible to
>> open multiple message frames and delete each frame automatically
>> after sending it.

Thanks again for this. I've been using it since you posted it and I
like it very much. There's only one minor disturbance: I often put
messages in the drafts group and send them later (without further
editing) with `D s' (`gnus-draft-send-message'). With your
configuration, Emacs opens a new frame, sends the message and closes
the frame again. Is it possible to avoid the new frame, when sending
messages with `gnus-draft-send-message'?

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

Re: multiple message frames

[Katsumi Yamaoka]

Hi,

>>>>> In <v9elc0ejfz.fsf@marauder.physik.uni-ulm.de>
>>>>>	Reiner Steib <4uce.02.r.steib@gmx.net> wrote:

>>> This is my gnus-buffer-configuration...

> Thanks again for this. I've been using it since you posted it and I
> like it very much.

That is also my favorite. :)

> There's only one minor disturbance: I often put messages in the
> drafts group and send them later (without further editing) with `D
> s' (`gnus-draft-send-message'). With your configuration, Emacs opens
> a new frame, sends the message and closes the frame again. Is it
> possible to avoid the new frame, when sending messages with
> `gnus-draft-send-message'?

Oh, I see it.  I don't use gnus-draft normally, though.
The following hook may help you.  How about it?

(add-hook
 'gnus-message-setup-hook
 (lambda nil
   (if (memq this-command '(gnus-draft-send-message
			    gnus-draft-send-all-messages))
       (let ((config (copy-sequence gnus-buffer-configuration)))
	 (set (make-local-variable 'gnus-buffer-configuration)
	      (cons '(forward (vertical 1.0 (message 1.0 point)))
		    (delq (assq 'forward config) config)))
	 (set (make-local-variable 'gnus-configure-windows-hook)
	      nil)))))
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: multiple message frames

[Katsumi Yamaoka]

[-- Attachment #1: Type: text/plain, Size: 258 bytes --]

Hi,

This is the revised version of the "multiple message frames"
suit.  It makes it possible to open multiple message frames and
delete each frame automatically after sending or killing it.
You can use it by simply putting it in your .gnus.el file.
Enjoy!


[-- Attachment #2: Type: application/emacs-lisp, Size: 2690 bytes --]

Re: multiple message frames

[Andreas Fuchs]

Today, Katsumi Yamaoka <yamaoka@jpl.org> wrote:
> This is the revised version of the "multiple message frames"
> suit.  It makes it possible to open multiple message frames and
> delete each frame automatically after sending or killing it.
> You can use it by simply putting it in your .gnus.el file.
> Enjoy!

That's great! I've found myself wanting such a configuration for a very
long time.

Thank you,
-- 
Andreas Fuchs, <asf@acm.org>, asf@jabber.at, antifuchs
irc.freenode.net's #emacs - online emacs advice from IRC addicts