From: Miles Bader <miles@gnu.org>
To: ding@gnus.org
Subject: gnus-article-read-summary-keys: can't handle hidden summary buffer?
Date: Mon, 29 Sep 2008 13:29:51 +0900 [thread overview]
Message-ID: <buovdwfvakg.fsf@dhapc248.dev.necel.com> (raw)
If I select the article window, and hide the summary buffer (something I
often like to do while reading long threads), then many inter-article
movement commands give an error like:
gnus-article-read-summary-keys: Wrong type argument: window-live-p, #<window 44>
The commands still seem to pretty much do the right thing (for instance,
"n" still moves to the next message), but the constant error messages
are annoying (and presumably there are some minor functional differences
as well).
This used to work properly, with no error messages. I'm not really sure
when error messages started showing up, but sometime in the medium-past
(at least the last year or so I think?).
The stack backtrace is:
Debugger entered--Lisp error: (wrong-type-argument window-live-p #<window 52>)
window-buffer(#<window 52>)
(set-buffer (window-buffer win))
(save-current-buffer (set-buffer (window-buffer win)) (eq major-mode (quote gnus-summary-mode)))
(with-current-buffer (window-buffer win) (eq major-mode (quote gnus-summary-mode)))
(and (not not-restore-window) new-sum-point (with-current-buffer (window-buffer win) (eq major-mode ...)))
(if (and (not not-restore-window) new-sum-point (with-current-buffer ... ...)) (progn (set-window-point win new-sum-point) (set-window-start win new-sum-start) (set-window-hscroll win new-sum-hscroll)))
(when (and (not not-restore-window) new-sum-point (with-current-buffer ... ...)) (set-window-point win new-sum-point) (set-window-start win new-sum-start) (set-window-hscroll win new-sum-hscroll))
(progn (setq selected (gnus-summary-select-article)) (set-buffer obuf) (unless not-restore-window (set-window-configuration owin)) (when (and ... new-sum-point) (set-window-start ... 1) (set-window-point ... ...)) (when (and ... new-sum-point ...) (set-window-point win new-sum-point) (set-window-start win new-sum-start) (set-window-hscroll win new-sum-hscroll)))
(if (or (eq in-buffer ...) (when ... ... t)) (progn (setq selected ...) (set-buffer obuf) (unless not-restore-window ...) (when ... ... ...) (when ... ... ... ...)))
(when (or (eq in-buffer ...) (when ... ... t)) (setq selected (gnus-summary-select-article)) (set-buffer obuf) (unless not-restore-window (set-window-configuration owin)) (when (and ... new-sum-point) (set-window-start ... 1) (set-window-point ... ...)) (when (and ... new-sum-point ...) (set-window-point win new-sum-point) (set-window-start win new-sum-start) (set-window-hscroll win new-sum-hscroll)))
(progn (when (eq win ...) (setq new-sum-point ... new-sum-start ... new-sum-hscroll ...)) (when (or ... ...) (setq selected ...) (set-buffer obuf) (unless not-restore-window ...) (when ... ... ...) (when ... ... ... ...)))
(if (and (setq func ...) (functionp func) (condition-case code ... ...)) (progn (when ... ...) (when ... ... ... ... ... ...)) (set-window-configuration owin) (if err (signal ... ...) (ding)))
(let ((obuf ...) (owin ...) win func in-buffer selected new-sum-start new-sum-hscroll err) (cond (not-restore-window ... ...) (... ...) (t ...)) (setq in-buffer (current-buffer)) (if (and ... ... ...) (progn ... ...) (set-window-configuration owin) (if err ... ...)))
(cond ((eq ... 8) (gnus-article-describe-bindings ...)) ((or ... ... ...) (let ... ... ... ...)) (t (let ... ... ... ...)))
(let ((nosaves ...) (nosave-but-article ...) (nosave-in-article ...) (up-to-top ...) keys new-sum-point) (with-current-buffer gnus-article-current-summary (let ... ...)) (message "") (cond (... ...) (... ...) (t ...)))
gnus-article-read-summary-keys(nil)
call-interactively(gnus-article-read-summary-keys nil nil)
Thanks,
-Miles
--
The secret to creativity is knowing how to hide your sources.
--Albert Einstein
next reply other threads:[~2008-09-29 4:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 4:29 Miles Bader [this message]
2008-09-29 11:08 ` Katsumi Yamaoka
2008-09-29 12:20 ` Miles Bader
2008-09-29 23:55 ` Katsumi Yamaoka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=buovdwfvakg.fsf@dhapc248.dev.necel.com \
--to=miles@gnu.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).