Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: jeff.rancier@softechnics.com (Jeffery B. Rancier)
Subject: Re: possible to generate .overview file for nnml: group?
Date: 24 Dec 2002 12:36:20 -0500	[thread overview]
Message-ID: <uptrrl3or.fsf@softechnics.com> (raw)
In-Reply-To: <uu1h3l5ln.fsf@softechnics.com>

Answering my own ...

I did a C-u M-x apropos gnus, then searched the buffer for "overview",
and nothing, another search for generate revealed:

,----[ C-h f nnml-generate-nov-databases RET ]
| nnml-generate-nov-databases is an interactive compiled Lisp function in `c:/usr/pkg/emacs-21.2/lisp/gnus/nnml.elc'.
| (nnml-generate-nov-databases)
| 
| Generate NOV databases in all nnml directories.
`----

Jeff

>>>>> "JBR" == Jeffery B Rancier <jeff.rancier@softechnics.com> writes:

    JBR> Hi All.  After creating a new nnml: group, I have just the
    JBR> message in the directory.  When selecting the group, I get
    JBR> all the messages without a problem.  When I move a new
    JBR> message into the group, a .overfile is then generated.  At
    JBR> that point retrieving the old messages show only the newly
    JBR> added messages.  If I delete the .overview, I can again see
    JBR> all the messages.  Deleting the .overview everytime I add a
    JBR> new message doesn't seem like the correct approach.  Is there
    JBR> a way to generate the .overview file?
    JBR> --

    JBR> Thanks, Jeff ,---- | Jeffery B. Rancier
    JBR> | 
    JBR> | Softechnics
    JBR> | a METTLER TOLEDO company
    JBR> `----

-- 

Thanks,
Jeff
,----
| Jeffery B. Rancier
| 
| Softechnics
| a METTLER TOLEDO company
`----


           reply	other threads:[~2002-12-24 17:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <uu1h3l5ln.fsf@softechnics.com>]

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=uptrrl3or.fsf@softechnics.com \
    --to=jeff.rancier@softechnics.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).