- (progn
- ;; This loops if any members of the inbox list have the same
- ;; basename (see "name conflict" below).
- (while all-files
- (let ((opoint (point))
- ;; If buffer has not changed yet, and has not been
- ;; saved yet, don't replace the old backup file now.
- (make-backup-files (and make-backup-files (buffer-modified-p)))
- (buffer-read-only nil)
- ;; Don't make undo records while getting mail.
- (buffer-undo-list t)
- delete-files success files file-last-names)
- ;; Pull files off all-files onto files as long as there is
- ;; no name conflict. A conflict happens when two inbox
- ;; file names have the same last component.
- ;; FIXME why does this "conflict" need kid gloves?
+ (progn
+ ;; This loops if any members of the inbox list have the same
+ ;; basename (see "name conflict" below).
+ (while all-files
+ (let ((opoint (point))
+ ;; If buffer has not changed yet, and has not been
+ ;; saved yet, don't replace the old backup file now.
+ (make-backup-files (and make-backup-files (buffer-modified-p)))
+ (buffer-read-only nil)
+ ;; Don't make undo records while getting mail.
+ (buffer-undo-list t)
+ delete-files success files file-last-names)
+ ;; Pull files off all-files onto files as long as there is
+ ;; no name conflict. A conflict happens when two inbox
+ ;; file names have the same last component.
+ ;; The reason this careful handling is necessary seems
+ ;; to be that rmail-insert-inbox-text uses .newmail-BASENAME.