Gnus development mailing list
 help / color / mirror / Atom feed
From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Subject: Re: PATCH: Skip over ticked articles in summary buffer
Date: 17 Apr 1997 11:29:12 +0200	[thread overview]
Message-ID: <tj4td6gfpz.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Aharon Schkolnik's message of 15 Apr 1997 10:55:55 +0300

After some discussion with Aharon, I would like to make a couple of
suggestions.

First, I like Aharon's idea that I should be able to enter a group and
be positioned on an article but without actually opening it.  This is
somewhat possible with the variable `gnus-auto-select-first'.  If its
value is `nil' then I enter the group with the cursor over the very
first article in the buffer, `best' positions the cursor on the
article with the highest score _and_ opens it.  Anything else
positions the cursor on the first unread article _and_ opens it.
Aharon's patch (`position') positions the cursor on the first unread
article but does not open it.  All of this leads me to the conclusion
that this poor variable has too many things to do :-)

What if instead, there were two variables - 1 to determine which
article the cursor would be positioned on (`nil' = first in buffer,
`best' = article with the highest score, anything else = the first
unread article) and 2 to determine independently whether that article
should be opened/shown/selected.

Second, this only controls the initial entry into the group.  The `.'
key (in the summary buffer) selects the next unread article, ','
selects the next best article, `N' selects the very next article.
These all move the cursor _and_ open the article.  I would like a way
to move to the next article _without_ opening it.  Sometimes I just
want to see what article is next but I don't want to open it because I
might decide simply from the subject that I don not want to read it
and therefore (if I'm using scoring) I do not want it to get
registered as an article that I chose to read.  Plus if its large and
far away I don't want to suck it across the net.  One way to do this
would be to have a variable setting so that (for instance) `.' would
only position the cursor and I would have to use `space' to open it.
Another possibility would be to toggle this behavior with `C-u .'.  So
in some groups I might want to never open articles by default but in
others I might want the opposite behavior and a `C-u' prefix would
allow me to override the current behavior.


  reply	other threads:[~1997-04-17  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-13  4:42 How to skip over ticked articles in summary buffer ? Aharon Schkolnik
1997-04-13  9:32 ` John Griffith
1997-04-13 10:29   ` David Moore
1997-04-13 10:53     ` John Griffith
1997-04-13 11:10     ` Hrvoje Niksic
     [not found] ` <nragcyeq3.fsf@healdb.matat.health.gov.il>
1997-04-15  7:55   ` PATCH: Skip over ticked articles in summary buffer Aharon Schkolnik
1997-04-17  9:29     ` John Griffith [this message]
1997-04-17 11:14       ` Steinar Bang
1997-04-17 11:21         ` Steinar Bang
1997-04-18 17:56           ` robert_pluim
1997-04-19  1:59       ` 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=tj4td6gfpz.fsf@sfs.nphil.uni-tuebingen.de \
    --to=griffith@sfs.nphil.uni-tuebingen.de \
    /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).