From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/15822 Path: main.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.gnus.general Subject: Re: Strange 'n' behavior Date: 04 Aug 1998 12:43:12 -0700 Sender: owner-ding@hpc.uh.edu Message-ID: References: <76zpdklqd6.fsf@ppllc.com> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035154792 24218 80.91.224.250 (20 Oct 2002 22:59:52 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 22:59:52 +0000 (UTC) Return-Path: Original-Received: from gwyn.tux.org (gwyn.tux.org [207.96.122.8]) by altair.xemacs.org (8.9.1/8.9.1) with ESMTP id MAA02464 for ; Tue, 4 Aug 1998 12:53:08 -0700 Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by gwyn.tux.org (8.8.8/8.8.8) with ESMTP id PAA30343 for ; Tue, 4 Aug 1998 15:48:39 -0400 Original-Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.7.6/8.7.3) with ESMTP id OAT01686; Tue, 4 Aug 1998 14:19:46 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Tue, 04 Aug 1998 14:46:16 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id OAA11609 for ; Tue, 4 Aug 1998 14:46:08 -0500 (CDT) Original-Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id PAA08248 for ; Tue, 4 Aug 1998 15:45:54 -0400 (EDT) Original-Received: from localhost (pm1-16.sba1.avtel.net [207.71.218.66]) by beach.silcom.com (8.9.0/8.9.0) with ESMTP id MAA19871 for ; Tue, 4 Aug 1998 12:47:36 -0700 (PDT) Original-To: ding@gnus.org In-Reply-To: Jake Colman's message of "04 Aug 1998 11:27:01 -0400" Original-Lines: 14 X-Mailer: Gnus v5.6.28/Emacs 20.2 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:15822 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:15822 Jake Colman writes: > When I press 'n' in a Summary Buffer I would expect to move to the next > unread message in the thread or the first unread message in the next thread. > Instead, after reading all messages in a thread, an 'n' command moves me to > the earliest unread message of the Summary Buffer - essentially moving me > backwards instead of forwards. Is this to be expected? > I had that once -- it took me while to see I had capslock on. -- Harry Putnam reader@newsguy.com