Commit f266826b authored by David Byers's avatar David Byers
Browse files

Fixed bug 664.

Detailed changes:
> 	Fix bug 664:
> 	* option-edit.el (lyskom-custom-variables): Support third value
> 	for kom-pop-personal-messages.
>
> 	* async.el (lyskom-handle-as-personal-message): If
> 	kom-pop-personal-messages is non-nil and non-t, don't pop up
> 	the frame.
>
> 	* buffers.el (lyskom-display-buffer): Added parameter
> 	keep-frame-iconfiied.
>
parent 2f3b9b69
2003-04-05 David Byers <david.byers@swipnet.se>
Fix bug 664:
* option-edit.el (lyskom-custom-variables): Support third value
for kom-pop-personal-messages.
* async.el (lyskom-handle-as-personal-message): If
kom-pop-personal-messages is non-nil and non-t, don't pop up
the frame.
* buffers.el (lyskom-display-buffer): Added parameter
keep-frame-iconfiied.
Fix bug 742:
* commands2.el (kom-will-person-read-text): New command.
......
......@@ -584,7 +584,8 @@ converted, before insertion."
(lyskom-insert string )
(if pop
(save-selected-window
(select-window (lyskom-display-buffer (current-buffer)))
(select-window (lyskom-display-buffer (current-buffer)
(not (eq pop t))))
(goto-char (point-max))
(recenter -1))))))))))
......
......@@ -426,13 +426,16 @@ to all children"
(defun lyskom-display-buffer (buffer)
(defun lyskom-display-buffer (buffer &optional keep-frame-iconified)
"Display the buffer BUFFER and select the window displaying it.
If BUFFER is already visible in some window in any frame, iconified or
otherwise, make that window visible. Otherwise display buffer as per
which category it is in. Selects the window.
If optional argument KEEP-FRAME-ICONIFIED is non-nil, then don't
deiconify any frames.
Returns the window displaying BUFFER."
......@@ -461,7 +464,8 @@ Returns the window displaying BUFFER."
(cond
(visible-frame (select-window visible-frame)
visible-frame)
(iconified-frame (make-frame-visible (window-frame iconified-frame))
(iconified-frame (unless keep-frame-iconified
(make-frame-visible (window-frame iconified-frame)))
(select-window iconified-frame)
iconified-frame)
......
......@@ -2914,6 +2914,8 @@ Select whether to execute command or keyboard macro.")
(highlight-face . "Face:")
(highlight-conflist . "Conference list")
(yes-dont-pop . "Yes, but don't uniconify frames")
;;
;; Misc doc strings
;;
......
......@@ -655,7 +655,9 @@ customize buffer but do not save them to the server."
(choice ((const (messages-in-lyskom-buffer t))
(const (discard-messages nil))
(string nil :tag in-named-buffer :help-echo select-buffer))))
(kom-pop-personal-messages (toggle (yes no)))
(kom-pop-personal-messages (choice ((const (yes t))
(const (yes-dont-pop yes))
(const (no nil)))))
(kom-ding-on-new-letter (ding))
(kom-ding-on-priority-break (ding))
(kom-ding-on-wait-done (ding))
......
......@@ -3030,6 +3030,8 @@ teckenkodning.
(highlight-face . "Utseende:")
(highlight-conflist . "Mteslista")
(yes-dont-pop . "Ja, men avikonifiera inte fnstret")
;;
;; Misc doc strings
;;
......
......@@ -1488,11 +1488,13 @@ All values other than those listed are reserved for future use."
"**Non-nil means pop up a buffer with personal messages as they arrive.
When this variable is set to `nil', personal, group and alarm messages
are simply inserted in the appropriate buffer
\(see `kom-show-personal-messages-in-buffer'). The buffer is not
displayed automatically. When this variable is set to `t', the buffer
in which a new message is shown will be displayed automatically,
possibly splitting windows and uniconifying frames.
are simply inserted in the appropriate buffer \(see
`kom-show-personal-messages-in-buffer'). The buffer is not displayed
automatically. When this variable is set to `t', the buffer in which a
new message is shown will be displayed automatically, possibly
splitting windows and uniconifying frames. When this variable is set
to `yes', the behavior is identical to when it is set to `t', but
frames will not be uniconified.
Values other than `t' and `nil' are reserved for future use."
server)
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment