Error on 'k'illing last thread in Gnus

Error on 'k'illing last thread in Gnus

[Nevin Kapur]

Recently I sometimes get an error when I use 'k' to kill the last
thread in a group. Here's the backtrace:

,----
| Signaling: (wrong-type-argument windowp nil)
|   select-window(nil)
|   gnus-summary-next-article(t nil)
|   gnus-summary-kill-same-subject-and-select(nil)
|   call-interactively(gnus-summary-kill-same-subject-and-select)
`----

Anyone know what's going on? I have customized the window
configurations using gnus-add-configuration, if that helps...

Thanks,
Nevin

Re: Error on 'k'illing last thread in Gnus

[ShengHuo ZHU]

Nevin Kapur <nkapur@bellatlantic.net> writes:

> Recently I sometimes get an error when I use 'k' to kill the last
> thread in a group. Here's the backtrace:
> 
> ,----
> | Signaling: (wrong-type-argument windowp nil)
> |   select-window(nil)
> |   gnus-summary-next-article(t nil)
> |   gnus-summary-kill-same-subject-and-select(nil)
> |   call-interactively(gnus-summary-kill-same-subject-and-select)
> `----
> 
> Anyone know what's going on? I have customized the window
> configurations using gnus-add-configuration, if that helps...

In gnus-summary-next-article, Gnus switch to the group buffer then
back to the summary buffer.  Customized window configurations could
cause Gnus miss the summary buffer window.  Posting your
configurations might help to find out this bug.

ShengHuo

Re: Error on 'k'illing last thread in Gnus

[Nevin Kapur]

>>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:

 ZSH> Nevin Kapur <nkapur@bellatlantic.net> writes:
 >> Recently I sometimes get an error when I use 'k' to kill the last
 >> thread in a group. Here's the backtrace:
 
 [...]

 >> Anyone know what's going on? I have customized the window
 >> configurations using gnus-add-configuration, if that helps...

 ZSH> In gnus-summary-next-article, Gnus switch to the group buffer
 ZSH> then back to the summary buffer.  Customized window
 ZSH> configurations could cause Gnus miss the summary buffer window.
 ZSH> Posting your configurations might help to find out this bug.

Here's my window configuration:

(defun NK::gnus-wide-config ()
  "*Definitions of window usage: Wide screens."
  (interactive)
  ;; (shell)
  (diary)
  (records-goto-today)
  (gnus-add-configuration
   '(summary
     (horizontal 1.0
		 (vertical 1.0 (group 0.25) (summary 1.0 point)))))
  (gnus-add-configuration
   '(article
     (horizontal 1.0
		 (vertical 0.47 (summary 1.0 point))
		 (vertical 1.0  (article 1.0)))))
  (gnus-add-configuration
   '(message
     (horizontal 1.0 (message 1.0 point) ("*shell*" 0.5))))
  (gnus-add-configuration
   '(reply
     (horizontal 1.0
		 (article 0.5) (message 1.0 point))))
  (gnus-add-configuration
   '(reply-yank
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0))
		 (vertical 1.0 (message 1.0 point)))))
  (gnus-add-configuration
   '(post
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0))
		 (vertical 1.0 (post 1.0 point)))))
  (gnus-add-configuration
   '(forward
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0))
		 (vertical 1.0 (message 1.0 point)))))
  (gnus-add-configuration
   '(edit-score
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0))
		 (vertical 1.0 (edit-score 1.0 point)))))
  (gnus-add-configuration
   '(score-trace
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0 point))
		 (vertical 1.0 ("*Score Trace*" 0.25) (article 1.0)))))
  (gnus-add-configuration
   '(mail-forward
     (horizontal 1.0
		 (vertical 0.47 (group 0.25) (summary 1.0))
		 (vertical 1.0 (mail 1.0 point)))))
  (gnus-add-configuration
   `(group
     (horizontal 1.0
		 (vertical 0.47 
			   (group 1.0 point) ("*Fancy Diary Entries*" 0.30))
		 (vertical 1.0 (,(records-todays-date) 1.0) ("*Calendar*" 0.22)))))


This function is called once on startup.

Thanks,
Nevin