Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: nnmh, delete next last article (Was: Re: Can't select group created by copying)
Date: 09 Jul 1999 09:54:58 +0200	[thread overview]
Message-ID: <vaf7loa6ywd.fsf@petty.cs.uni-dortmund.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "08 Jul 1999 15:26:10 -0400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> * Kai.Grossjohann@CS.Uni-Dortmund.DE  on Thu, 08 Jul 1999
> | Oh.  Strange.  Hm.  Bug in pgnus?
> 
> Well, if you use nnml/nnmh, Gnus will generally not delete the last message
> just in case you happen to be using procmail.  It sounds like the variable
> (or whatever) that tells Gnus what the last message number might be is not
> being updated.

That's what I thought, too, but the original poster explained that
it's the _next to last_ msg which isn't deleted, rather than the
_last_ one.

kai
-- 
Life is hard and then you die.


  reply	other threads:[~1999-07-09  7:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-07 10:32 Can't select group created by copying Jon K Hellan
1999-07-07 13:51 ` Jon K Hellan
1999-07-07 19:15   ` Simon Josefsson
1999-07-07 20:44     ` Jon K Hellan
1999-07-08 11:45   ` Jon K Hellan
1999-07-08 11:52     ` Jon K Hellan
     [not found] ` <wtnzp18a9wb.fsf@licia.dtek.chalmers.se>
1999-07-07 13:56   ` Jon K Hellan
1999-07-07 14:00   ` Kai.Grossjohann
     [not found]     ` <wtnr9mkph6s.fsf_-_@licia.dtek.chalmers.se>
1999-07-08  9:37       ` nnmh, delete next last article (Was: Re: Can't select group created by copying) Kai.Grossjohann
1999-07-08 19:26         ` Stainless Steel Rat
1999-07-09  7:54           ` Kai.Grossjohann [this message]
1999-07-09 18:56             ` Stainless Steel Rat
     [not found]             ` <wtng12ytcb0.fsf@licia.dtek.chalmers.se>
     [not found]               ` <wtnr9m6t6qk.fsf@licia.dtek.chalmers.se>
1999-08-27 19:57                 ` Lars Magne Ingebrigtsen
1999-07-09 17:16           ` 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=vaf7loa6ywd.fsf@petty.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).