From: Kohkichi Hosoda <khosoda@venus.dti.ne.jp>
Cc: ding@gnus.org
Subject: Re: Spam does not move
Date: Sun, 27 Jun 2004 01:19:36 +0900 [thread overview]
Message-ID: <m3isde8f6t.fsf@venus.dti.ne.jp> (raw)
In-Reply-To: <4nzn6s6hro.fsf@lifelogs.com> (Ted Zlatanov's message of "24 Jun 2004 12:30:03 -0400")
>>>>> On 24 Jun 2004 12:30:03 -0400, "Ted Zlatanov" <tzz@lifelogs.com> said:
Ted> I'm pretty sure this is not a problem with spam.el, but either
Ted> with your configuration or with another part of Gnus (maybe the
Ted> agent?)
Ted> Put this:
Ted> (debug (spam-list-articles gnus-newsgroup-articles 'spam))
Ted> at line 1296 of spam.el
First of all, thank you very much for taking care of my persistent
problem. I tried this in my mail group, marked a mail with M-d,
exited the summary buffer, and got the following messages.
Debugger entered: nil
(if gnus-group-is-exiting-without-update-p nil (gnus-message 6 "Exiting summary buffer and applying spam rules") (dolist (classification ...) (let* ... ...)) (debug (spam-list-articles gnus-newsgroup-articles ...)) (dolist (backend-type ...) (dolist ... ...)) (dolist (article ...) (gnus-summary-mark-article article gnus-expirable-mark)))
(unless gnus-group-is-exiting-without-update-p (gnus-message 6 "Exiting summary buffer and applying spam rules") (dolist (classification ...) (let* ... ...)) (debug (spam-list-articles gnus-newsgroup-articles ...)) (dolist (backend-type ...) (dolist ... ...)) (dolist (article ...) (gnus-summary-mark-article article gnus-expirable-mark)))
spam-summary-prepare-exit()
run-hooks(gnus-summary-prepare-exit-hook)
apply(run-hooks gnus-summary-prepare-exit-hook)
gnus-run-hooks(gnus-summary-prepare-exit-hook)
gnus-summary-exit()
* call-interactively(gnus-summary-exit)
On the other hand, I got the following messages when I exited the
summary buffer of spam group.
Debugger entered: ((22836 22835 22834 22833 22832 22831 22830))
(if gnus-group-is-exiting-without-update-p nil (gnus-message 6 "Exiting summary buffer and applying spam rules") (dolist (classification ...) (let* ... ...)) (debug (spam-list-articles gnus-newsgroup-articles ...)) (dolist (backend-type ...) (dolist ... ...)) (dolist (article ...) (gnus-summary-mark-article article gnus-expirable-mark)))
(unless gnus-group-is-exiting-without-update-p (gnus-message 6 "Exiting summary buffer and applying spam rules") (dolist (classification ...) (let* ... ...)) (debug (spam-list-articles gnus-newsgroup-articles ...)) (dolist (backend-type ...) (dolist ... ...)) (dolist (article ...) (gnus-summary-mark-article article gnus-expirable-mark)))
spam-summary-prepare-exit()
run-hooks(gnus-summary-prepare-exit-hook)
apply(run-hooks gnus-summary-prepare-exit-hook)
gnus-run-hooks(gnus-summary-prepare-exit-hook)
gnus-summary-exit()
* call-interactively(gnus-summary-exit)
I also checked gnus-newsgroup-articles.
C-h v gnus-newsgroup-articles demonstrated;
gnus-newsgroup-articles's value is
(272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572)
Local in buffer *Summary nnml:ding*; global value is nil
This seems normal to me.
Sincerely,
--
Kohkichi Hosoda
E-mail address: khosoda@venus.dti.ne.jp
http://www.venus.dti.ne.jp/~khosoda/Enlightenment.html
next prev parent reply other threads:[~2004-06-26 16:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-17 12:47 Kohkichi Hosoda
2004-05-17 15:17 ` Reiner Steib
2004-05-18 14:55 ` Kohkichi Hosoda
2004-05-18 15:40 ` Kai Grossjohann
2004-05-19 15:31 ` Kohkichi Hosoda
2004-05-19 18:07 ` Ted Zlatanov
2004-05-21 13:16 ` Kohkichi Hosoda
2004-05-22 14:11 ` Kohkichi Hosoda
2004-05-24 19:10 ` Ted Zlatanov
2004-05-28 17:00 ` Kohkichi Hosoda
2004-06-14 16:07 ` Ted Zlatanov
2004-06-18 16:00 ` Kohkichi Hosoda
2004-06-24 16:30 ` Ted Zlatanov
2004-06-26 14:05 ` Kohkichi Hosoda
2004-06-26 16:19 ` Kohkichi Hosoda [this message]
2004-06-29 18:16 ` Ted Zlatanov
2004-07-01 13:21 ` Kohkichi Hosoda
2004-07-01 16:11 ` Ted Zlatanov
2004-07-02 13:11 ` Kohkichi Hosoda
2004-07-16 17:00 ` Ted Zlatanov
2004-07-25 14:29 ` Kohkichi Hosoda
2004-07-27 16:46 ` Ted Zlatanov
2004-08-14 14:15 ` Kohkichi Hosoda
-- strict thread matches above, loose matches on Subject: below --
2004-05-16 13:20 Kohkichi Hosoda
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=m3isde8f6t.fsf@venus.dti.ne.jp \
--to=khosoda@venus.dti.ne.jp \
--cc=ding@gnus.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).