Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Vasily Korytov <deskpot@myrealbox.com>
Subject: Re: saving downloaded posts
Date: Mon, 11 Nov 2002 02:07:24 +0300	[thread overview]
Message-ID: <87d6pd9g7n.fsf@unix.home> (raw)
In-Reply-To: <3dcee01a$1@news.swissonline.ch>

>>>>> "m" == mac  writes:

 m> When I use gnus it will happen like this? : *until 4 the same*
 m> 1. I subscribe to a group
 m> 2. I download all header
 m> 3. I can mark them as important ... read or however
 m> 4. I exit from there
 m> .
 m> 5. When I reenter:
 -> I can *by default* not read already read messages

Correct. They're suppressed for display in favor of the new ones. Why
representing again those read messages -- there may be really many of
them and it may slow down the process and make the screen much more
messy.

But if you want to see, say, 97 read messages while there're 3 unread,
enter the group with C-u 100 (ret|space). If you want to see both new
and old, but all of them, emit 100. That's simply C-u (ret|space).

So, you can read them, but they're not displayed by default -- and I
think, that's made for a good reason. If you used some other newsreader
(say, slrn; IMO, Mozilla doesn't look much like MUA or newsreader, as
well as Outlook -- and therefore it shouldn't be used as such), you'd
notice, this is a common behaviour.

 -> Messages which I did not read before, I have to  download again

Err... ``Download'' -- what do you mean? Do you use agent or what?

 m> Well I know this behaviour can be changed, but it's the default isn't
 m> it, and therefore also the common way people read news with gnus?

``The common way'' is simply to either read or kill all the new news, so
there're no new ones remaining.

-- 
                     With respect, Vasily Korytov

PGP key fingerprint: 123A 7CCE 6E26 6233 0D87 E01A A0F8 3524 FCD8 1841


  parent reply	other threads:[~2002-11-10 23:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3dcdbaf3$1@news.swissonline.ch>
     [not found] ` <y68smyaf7ok.fsf@multics.mit.edu>
2002-11-10  8:07   ` Abhijit Rao
     [not found]     ` <87r8dtvez5.fsf@unix.home>
     [not found]       ` <3dcee01a$1@news.swissonline.ch>
2002-11-10 23:07         ` Vasily Korytov [this message]
2002-11-11  0:14           ` calmar
2002-11-10 11:51 ` Reiner Steib

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=87d6pd9g7n.fsf@unix.home \
    --to=deskpot@myrealbox.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).