From: Michael Shields <shields@msrl.com>
Subject: Re: [PATCH] Skip over citations and signature (resend)
Date: Wed, 12 Feb 2003 17:55:42 +0000 [thread overview]
Message-ID: <87n0l1759d.fsf@mulligatwani.msrl.com> (raw)
In-Reply-To: <87smuvh2gm.fsf@mulligatwani.msrl.com> (Michael Shields's message of "Tue, 11 Feb 2003 04:21:29 +0000")
This patch goes with it also. I forget if it's required for my
skip-boring patch, but it seems like a good idea anyway.
2003-02-12 Michael Shields <shields@msrl.com>
* gnus-sum.el (gnus-article-goto-next-page,
gnus-article-goto-prev-page): Call gnus-summary-*-page, instead of
relying on the summary bindings of `n' and `p'.
Index: lisp/gnus-art.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-art.el,v
retrieving revision 6.293
diff -u -r6.293 gnus-art.el
--- lisp/gnus-art.el 12 Feb 2003 15:06:16 -0000 6.293
+++ lisp/gnus-art.el 12 Feb 2003 18:03:15 -0000
@@ -4686,15 +4695,14 @@
(defun gnus-article-goto-next-page ()
"Show the next page of the article."
(interactive)
- (when (gnus-article-next-page)
- (goto-char (point-min))
- (gnus-article-read-summary-keys nil (gnus-character-to-event ?n))))
+ (gnus-eval-in-buffer-window gnus-summary-buffer
+ (gnus-summary-next-page)))
(defun gnus-article-goto-prev-page ()
"Show the next page of the article."
(interactive)
- (if (bobp) (gnus-article-read-summary-keys nil (gnus-character-to-event ?p))
- (gnus-article-prev-page nil)))
+ (gnus-eval-in-buffer-window gnus-summary-buffer
+ (gnus-summary-prev-page)))
(defun gnus-article-next-page (&optional lines)
"Show the next page of the current article.
--
Shields.
next prev parent reply other threads:[~2003-02-12 17:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 4:21 Michael Shields
2003-02-12 14:58 ` Kai Großjohann
2003-02-12 17:55 ` Michael Shields [this message]
2003-02-12 20:21 ` Kai Großjohann
2003-04-09 21:42 ` Jesper Harder
2003-04-09 23:23 ` Michael Shields
2003-04-10 0:06 ` Jesper Harder
2003-02-12 20:26 ` Kai Großjohann
2003-02-12 23:30 ` Michael Shields
2003-02-13 11:29 ` Kai Großjohann
2003-02-12 22:08 ` Frank Haun
2003-02-13 0:34 ` Katsumi Yamaoka
2003-02-13 1:07 ` Frank Haun
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=87n0l1759d.fsf@mulligatwani.msrl.com \
--to=shields@msrl.com \
/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).