Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Gijs Hillenius <gijs@hillenius.net>
To: info-gnus-english@gnu.org
Subject: FIXED Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around
Date: Mon, 18 Jan 2016 09:08:02 +0100	[thread overview]
Message-ID: <871t9fux7h.fsf@hillenius.net> (raw)
In-Reply-To: <mailman.2152.1452527287.843.info-gnus-english@gnu.org>

On 11 Jan 2016, Adam Sjøgren wrote:

> Gijs writes:
>
>> Is there some kind of debug flag I can switch on, to see what gnus &
>> bbdb are doing in fancy-split
>
> B t gives you a trace, B q show you where the email you are on will be
> split to.
>
> Otherwise it sounds like you need to go to edebug-defun...

using edebug was great, coz it shows my Gnus configuration works
fine. The last lines al return nil, which points to Gnus copying the
message succesfully and marking the original for deletion . So the
problem lay elsewhere.

I think I fixed it, in Cyrus, by running Squat and recreating an index
of my INBOX. I'm not sure that was it, but now the invisible' messages
are being removed.



      parent reply	other threads:[~2016-01-18  8:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 11:04 Gijs Hillenius
2016-01-05 11:17 ` Eric Abrahamsen
2016-01-05 11:26 ` CHENG Gao
2016-01-05 12:38 ` Gijs Hillenius
2016-01-05 12:54   ` Eric Abrahamsen
     [not found]   ` <mailman.1737.1451998456.843.info-gnus-english@gnu.org>
2016-01-05 13:07     ` Gijs Hillenius
2016-01-05 13:24       ` Eric Abrahamsen
     [not found]       ` <mailman.1740.1452000295.843.info-gnus-english@gnu.org>
2016-01-05 14:16         ` Gijs Hillenius
2016-01-05 14:48           ` Gijs Hillenius
2016-01-05 15:11             ` Eric Abrahamsen
     [not found]             ` <mailman.1745.1452006719.843.info-gnus-english@gnu.org>
2016-01-07  7:28               ` Gijs Hillenius
2016-01-07  8:54                 ` Eric Abrahamsen
     [not found]                 ` <mailman.1877.1452156877.843.info-gnus-english@gnu.org>
2016-01-07  9:14                   ` Gijs Hillenius
2016-01-07 14:03                     ` Eric Abrahamsen
     [not found]                     ` <mailman.1882.1452175419.843.info-gnus-english@gnu.org>
2016-01-08  7:54                       ` is this a bug in gnus v5.13? " Gijs Hillenius
2016-01-08 10:33                         ` Eric Abrahamsen
     [not found]                         ` <mailman.1947.1452249217.843.info-gnus-english@gnu.org>
2016-01-08 11:27                           ` Gijs Hillenius
2016-01-09  4:02                             ` Eric Abrahamsen
2016-01-09  9:44                               ` Adam Sjøgren
2016-01-11  6:56                                 ` Eric Abrahamsen
2016-01-11  9:28                                   ` Adam Sjøgren
     [not found]                               ` <mailman.2029.1452332680.843.info-gnus-english@gnu.org>
2016-01-11  9:29                                 ` Gijs Hillenius
2016-01-11  9:33                                   ` Adam Sjøgren
2016-01-11  9:40                                   ` Eric Abrahamsen
     [not found]                                   ` <mailman.2130.1452505220.843.info-gnus-english@gnu.org>
2016-01-11 11:34                                     ` Gijs Hillenius
2016-01-11 11:48                                       ` Adam Sjøgren
     [not found]                                       ` <mailman.2136.1452512951.843.info-gnus-english@gnu.org>
2016-01-11 12:54                                         ` Gijs Hillenius
2016-01-11 13:18                                         ` Gijs Hillenius
2016-01-11 15:47                                           ` Adam Sjøgren
     [not found]                                           ` <mailman.2152.1452527287.843.info-gnus-english@gnu.org>
2016-01-18  8:08                                             ` Gijs Hillenius [this message]

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=871t9fux7h.fsf@hillenius.net \
    --to=gijs@hillenius.net \
    --cc=info-gnus-english@gnu.org \
    /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).