From: Henrik Enberg <henrik@enberg.org>
Subject: Re: gnus-summary-prev-page dead?
Date: Mon, 30 Dec 2002 19:32:27 +0100 [thread overview]
Message-ID: <878yy74atg.fsf@enberg.org> (raw)
In-Reply-To: <m3wulrmrq9.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 30 Dec 2002 16:49:50 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Henrik Enberg <henrik@enberg.org> writes:
>
>> Anyone else having problems with `gnus-summary-prev-page'? It has
>> stopped working completely for me. I suspect this might be an Emacs
>> CVS issue, but maybe this means Gnus needs to accommodate? I haven't
>> seen any other similar brokenness in Emacs.
>
> It seems to be working OK for me, but I'm using an older CVS
> version. (From half a year ago, I think.)
>
> Can you reproduce the bug in Emacs 21.2?
Nope, not with a month old CVS Emacs either. It is most likely related
to some changes in Emacs in the past week or so. Should I whine on the
Emacs list instead?
next prev parent reply other threads:[~2002-12-30 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 15:43 Henrik Enberg
2002-12-30 15:49 ` Lars Magne Ingebrigtsen
2002-12-30 18:32 ` Henrik Enberg [this message]
2002-12-30 18:53 ` Lars Magne Ingebrigtsen
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=878yy74atg.fsf@enberg.org \
--to=henrik@enberg.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).