comparison lisp/nnfolder.el @ 14040:187735b53d52

Comment fixes.
author Karl Heuer <kwzh@gnu.org>
date Fri, 05 Jan 1996 22:21:28 +0000
parents 178d730efae2
children 83f275dcd93a
comparison
equal deleted inserted replaced
14039:831c5fda97f4 14040:187735b53d52
40 40
41 (defvar nnfolder-active-file 41 (defvar nnfolder-active-file
42 (concat (file-name-as-directory nnfolder-directory) "active") 42 (concat (file-name-as-directory nnfolder-directory) "active")
43 "The name of the active file.") 43 "The name of the active file.")
44 44
45 ;; I renamed this variable to somehting more in keeping with the general GNU 45 ;; I renamed this variable to something more in keeping with the general GNU
46 ;; style. -SLB 46 ;; style. -SLB
47 47
48 (defvar nnfolder-ignore-active-file nil 48 (defvar nnfolder-ignore-active-file nil
49 "If non-nil, causes nnfolder to do some extra work in order to determine the true active ranges of an mbox file. 49 "If non-nil, causes nnfolder to do some extra work in order to determine the true active ranges of an mbox file.
50 Note that the active file is still saved, but it's values are not 50 Note that the active file is still saved, but it's values are not
564 ;; This method has a problem if you've accidentally let the active list get 564 ;; This method has a problem if you've accidentally let the active list get
565 ;; out of sync with the files. This could happen, say, if you've 565 ;; out of sync with the files. This could happen, say, if you've
566 ;; accidentally gotten new mail with something other than Gnus (but why 566 ;; accidentally gotten new mail with something other than Gnus (but why
567 ;; would _that_ ever happen? :-). In that case, we will be in the middle of 567 ;; would _that_ ever happen? :-). In that case, we will be in the middle of
568 ;; processing the file, ready to add new X-Gnus article number markers, and 568 ;; processing the file, ready to add new X-Gnus article number markers, and
569 ;; we'll run accross a message with no ID yet - the active list _may_not_ be 569 ;; we'll run across a message with no ID yet - the active list _may_not_ be
570 ;; ready for us yet. 570 ;; ready for us yet.
571 571
572 ;; To handle this, I'm modifying this routine to maintain the maximum ID seen 572 ;; To handle this, I'm modifying this routine to maintain the maximum ID seen
573 ;; so far, and when we hit a message with no ID, we will _manually_ scan the 573 ;; so far, and when we hit a message with no ID, we will _manually_ scan the
574 ;; rest of the message looking for any more, possibly higher IDs. We'll 574 ;; rest of the message looking for any more, possibly higher IDs. We'll
591 (active (car (cdr (assoc nnfolder-current-group 591 (active (car (cdr (assoc nnfolder-current-group
592 nnfolder-group-alist)))) 592 nnfolder-group-alist))))
593 activenumber activemin start end) 593 activenumber activemin start end)
594 (goto-char (point-min)) 594 (goto-char (point-min))
595 ;; 595 ;;
596 ;; Anytime the active number is 1 or 0, it is supect. In that case, 596 ;; Anytime the active number is 1 or 0, it is suspect. In that case,
597 ;; search the file manually to find the active number. Or, of course, 597 ;; search the file manually to find the active number. Or, of course,
598 ;; if we're being paranoid. (This would also be the place to build 598 ;; if we're being paranoid. (This would also be the place to build
599 ;; other lists from the header markers, such as expunge lists, etc., if 599 ;; other lists from the header markers, such as expunge lists, etc., if
600 ;; we ever desired to abandon the active file entirely for mboxes.) 600 ;; we ever desired to abandon the active file entirely for mboxes.)
601 (setq activenumber (cdr active)) 601 (setq activenumber (cdr active))