FIXED Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-18 Thread Gijs Hillenius
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

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Adam Sjøgren
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... Best regards, Adam -- "Jeg h

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Gijs Hillenius
Is there some kind of debug flag I can switch on, to see what gnus & bbdb are doing in fancy-split ___ info-gnus-english mailing list info-gnus-english@gnu.org https://lists.gnu.org/mailman/listinfo/info-gnus-english

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Gijs Hillenius
On 11 Jan 2016, Adam Sjøgren wrote: > Gijs writes: > >> The gnus/BBDB splits correctly but there are still invisible copies >> in the INBOX > > I don't know if it is relevant, but what value does nnmail-crosspost > have? setting nnmail-crosspost to nil has zilch effect, unfortunately

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Adam Sjøgren
Gijs writes: > The gnus/BBDB splits correctly but there are still invisible copies in > the INBOX I don't know if it is relevant, but what value does nnmail-crosspost have? ,[ C-h v nnmail-crosspost RET ] | nnmail-crosspost is a variable defined in `nnmail.el'. | Its value is nil | Original

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Gijs Hillenius
On 11 Jan 2016, Eric Abrahamsen wrote: [...] > Another option is: bbdb/gnus-nnimap-folder-list-from-bbdb. I used to > use that, and found it simpler and less mysterious. It just dumps a > bunch of splits wherever you use it. I think it's maybe less > configurable, but I found it sufficient, and

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Eric Abrahamsen
Gijs Hillenius writes: > On 9 Jan 2016, Adam Sjøgren wrote: > >> [...trim your quotes, folks...] > > ok! > > > [...] > >>> `bbdb/gnus-split-method'. The comments in bbdb-gnus indicate that >>> you're supposed to do something like this: >>> >>> (setq nnmail-split-methods 'bbdb/gnus-split-method)

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Adam Sjøgren
Gijs writes: > Added them this morning, ran a few tests the past hours, but my messages > continue to get split correctly, with erroneous copies remaining > invisible in the INBOX. Note that I don't use splitting with IMAP, so take what ever I say with an extra grain of salt... O:-), Ada

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Gijs Hillenius
On 9 Jan 2016, Adam Sjøgren wrote: > [...trim your quotes, folks...] ok! [...] >> `bbdb/gnus-split-method'. The comments in bbdb-gnus indicate that >> you're supposed to do something like this: >> >> (setq nnmail-split-methods 'bbdb/gnus-split-method) >> (setq bbdb/gnus-split-nomatch-function

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-11 Thread Adam Sjøgren
Eric writes: > Right, but the basic point remains that bbdb/gnus-split-method will > hijack the whole process unless you stop it -- though there are multiple > ways of stopping it. Anyhow, Gijs should have a few options to play with > now... You're right, the "put it into fancy-split lambda"-thin

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-10 Thread Eric Abrahamsen
a...@koldfront.dk (Adam Sjøgren) writes: > Eric writes: > > [...trim your quotes, folks...] > >> (setq nnimap-split-fancy >> '(| >> ("From" "googlealerts.*" "INBOX.google-alerts") >> (any "c[...]" "INBOX.tmp") >> ;; Invoke the BBDB >> (: (lambda () >> (car (bbd

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-09 Thread Adam Sjøgren
Eric writes: [...trim your quotes, folks...] > (setq nnimap-split-fancy > '(| > ("From" "googlealerts.*" "INBOX.google-alerts") > (any "c[...]" "INBOX.tmp") > ;; Invoke the BBDB > (: (lambda () >(car (bbdb/gnus-split-method > ;; Default mailbox

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-08 Thread Eric Abrahamsen
Gijs Hillenius writes: > On 8 Jan 2016, Eric Abrahamsen wrote: > >> Gijs Hillenius writes: >> >>> On 7 Jan 2016, Eric Abrahamsen wrote: >>> Gijs Hillenius writes: > [...] hope snipping this much is ok.. > >>> >>> If my Gnus (5.13, part of Debian's Emacs) copies messa

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-08 Thread Gijs Hillenius
On 8 Jan 2016, Eric Abrahamsen wrote: > Gijs Hillenius writes: > >> On 7 Jan 2016, Eric Abrahamsen wrote: >> >>> Gijs Hillenius writes: >>> [...] hope snipping this much is ok.. >> >> If my Gnus (5.13, part of Debian's Emacs) copies messages back >> into the INBOX, does f

Re: is this a bug in gnus v5.13? Re: gnus INBOX housekeeping, kept (copies of) mail lying around

2016-01-08 Thread Eric Abrahamsen
Gijs Hillenius writes: > On 7 Jan 2016, Eric Abrahamsen wrote: > >> Gijs Hillenius writes: >> >>> [...] hope snipping this much is ok.. >>> > > If my Gnus (5.13, part of Debian's Emacs) copies messages back into > the INBOX, does fancy-split set the delete/expunge IMAP flag to >