Gnus development mailing list
 help / color / mirror / Atom feed
From: Jake Colman <colman@ppllc.com>
Subject: Re: Strange 'n' behavior
Date: 04 Aug 1998 17:59:58 -0400	[thread overview]
Message-ID: <761zqwl869.fsf@ppllc.com> (raw)
In-Reply-To: Harry Putnam's message of "04 Aug 1998 12:43:12 -0700"

>>>>> "Harry" == Harry Putnam <reader@newsguy.com> writes:

   Harry> Jake Colman <colman@ppllc.com> 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?
   >> 

   Harry> I had that once -- it took me while to see I had capslock on.

   Harry> -- 

   Harry> Harry Putnam  reader@newsguy.com

Nope.  That's not it.  Nice try, though... :-)

-- 
Jake Colman                     

Principia Partners LLC                  Phone: (201) 946-0300
Harborside Financial Center               Fax: (201) 946-0320
902 Plaza II                           Beeper: (800) 505-2795
Jersey City, NJ 07311                  E-mail: colman@ppllc.com
                                       E-mail: jcolman@jnc.com
                                          web: http://www.ppllc.com


  reply	other threads:[~1998-08-04 21:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-04 15:27 Jake Colman
1998-08-04 19:43 ` Harry Putnam
1998-08-04 21:59   ` Jake Colman [this message]
1998-08-05  5:43 ` Lars Magne Ingebrigtsen
1998-08-05  6:38   ` Kai Grossjohann
1998-08-05  6:47     ` Lars Magne Ingebrigtsen
1998-08-05 13:34       ` Karl Kleinpaste
1998-08-05 19:51         ` Jake Colman
1998-08-06  0:13         ` Lars Magne Ingebrigtsen
1998-08-05 13:54       ` Jake Colman
1998-08-05 13:56         ` Kai Grossjohann
1998-08-06  0:14         ` 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=761zqwl869.fsf@ppllc.com \
    --to=colman@ppllc.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).