Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: Re: many keys have preconceived notions that one reads downward
Date: 26 Jan 2003 12:46:31 +0800	[thread overview]
Message-ID: <87vg0c4ixk.fsf@jidanni.org> (raw)

> Challenge for Lars for a week: read messages starting at the bottom of
> the buffer and advancing upwards with 'p'.  You'll find that many keys
> have preconceived notions that we are supposed to move down, like E.

< Virtually all the commands work that way.
< 
< Actually, this would be quite easy to fix, I think.  All the
< functions (eventually) call `gnus-summary-next-subject' and
< `gnus-summary-prev-subject' to move to the next/prev article.  There
< could be a command to toggle which direction these two functions
< actually moved -- then all the commands would (as if by magic) move
< point in the opposite direction that they normally do.
< 
Ok, but remember to be like one of those socket wrenches, where one
can set it for forward, reverse, and stationary -- three settings.

< Would that be useful, though?  Hitting `n' and going to the next
< message?  `SPC' down to the end of the message and then read the
< previous unread message?  Sounds pretty dubious to me.

What bugs me is  that when I hit E it is possible for the cursor to
jump 100s of messages forward, as it is looking for the next new message.
-- 
http://jidanni.org/ Taiwan(04)25854780


             reply	other threads:[~2003-01-26  4:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26  4:46 Dan Jacobson [this message]
     [not found] <87el74u7m9.fsf@jidanni.org>
2003-01-23 10:15 ` Kai Großjohann

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=87vg0c4ixk.fsf@jidanni.org \
    --to=jidanni@dman.ddts.net \
    /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).