From xemacs-m  Thu Mar  6 09:17:04 1997
Received: from berio.phx.mcd.mot.com ([144.191.25.196])
	by xemacs.org (8.8.5/8.8.5) with SMTP id JAA20292
	for <xemacs-beta@xemacs.org>; Thu, 6 Mar 1997 09:16:57 -0600 (CST)
Received: by berio.phx.mcd.mot.com (AIX 4.1/UCB 5.64/4.03)
          id AA18834; Thu, 6 Mar 1997 08:16:28 -0700
Date: Thu, 6 Mar 1997 08:16:28 -0700
Message-Id: <9703061516.AA18834@berio.phx.mcd.mot.com>
From: "Lynn D. Newton" <lnewton@berio.phx.mcd.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
To: XEmacs Beta Bugs <xemacs-beta@xemacs.org>
Subject: VM can't explode digest
Reply-To: lnewton@berio.phx.mcd.mot.com
Cc: randy_clayton@berio.phx.mcd.mot.com, steve_march@berio.phx.mcd.mot.com
Comments: Hyperbole mail buttons accepted, v04.01.
X-Face:  FVNLrR&aQu[q[N3kO<A5Au*4b"pWyOi13$\H%OVNM8&P{?7;KTRLXSU)c'&Gg3{7GD.p:05
 To5$NCN#r-;vs&Qi@jhk\a@l;bMgx77!GI>4+!:X-+LgxFf'("(:8&7z+:!,24n1@j?C25:p>hno)_
 hPa5S&WgH"E-!{{N^-Cx}MiI_O'dU0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by xemacs.org id JAA20300


------------------------------ my system -----------------------------
Editor:      XEmacs 19.15 (beta97) (powerpc-ibm-aix4.1.4.0)
OS Type:     aix4.1.4.0
Window Sys:  X
----------------------------------------------------------------------

I receive some list mail in digest form. On occasion I
attempt to burst it. This has always worked.


At present, I get a list of choices for digest type.
None work. If I accept 'guess', I get:

----------------- *Backtrace* buffer ------------------

  # bind (standard-output stack-trace-on-signal debug-on-signal stack-trace-on-error debug-on-error gobble-order dont-read-attributes)
  vm-assimilate-new-messages(t nil nil)
  # bind (start-buffer m totals-blurb mlist digest-type)
  #<compiled-function (from "vm.elc") (&optional digest-type) "...(242)" [digest-type vm-digest-burst-type vm-follow-summary-cursor vm-mail-buffer buffer-name error "Folder buffer has been killed." vm-check-for-killed-summary vm-error-if-folder-empty nil vm-select-marked-or-prefixed-messages 1 mlist totals-blurb m start-buffer vm-virtual-message-p 5 9 vm-folder-read-only signal folder-read-only "guess" vm-guess-digest-type "Couldn't guess digest type." message "Bursting %s digest..." "mime" vm-mime-burst-message "rfc934" vm-rfc934-burst-message "rfc1153" vm-rfc1153-burst-message "Unknown digest type: %s" "Bursting %s digest... done" vm-clear-modification-flag-undos vm-set-buffer-modified-p t vm-modification-counter vm-delete-after-bursting vm-move-after-deleting vm-delete-message vm-assimilate-new-messages 4 3 vm-update-summary-and-mode-line vm-emit-totals-blurb vm-display (vm-burst-digest vm-burst-mime-digest vm-burst-rfc934-digest vm-burst-rfc1153-digest) this-command vm-thoughtfully-select-message vm-preview-current-message] 6 "Burst the current message (a digest) into its individual messages.\nThe digest's messages are assimilated into the folder as new mail\nwould be.\n\nOptional argument DIGEST-TYPE is a string that tells VM what kind\nof digest the current message is.  If it is not given the value\ndefaults to the value of vm-digest-burst-type.  When called\ninteractively DIGEST-TYPE will be read from the minibuffer.\n\nIf invoked on marked messages (via vm-next-command-uses-marks),\nall marked messages will be burst." (list (let ... ... ...))>("guess")
  call-interactively(vm-burst-digest)
  # (condition-case ... . error)
  # (catch top-level ...)


last-error =>
(wrong-number-of-arguments #<compiled-function (from "hvm.elc") (&optional dont-read-attributes gobble-order) "...(242)" [vm-last vm-message-list nil new-messages b-list tail-cons buffer-size vm-sr-max vm-sr-min vm-sr-clip make-marker ((byte-code "~	
}	É
ÉÇ" [vm-sr-clip vm-sr-min vm-sr-max nil] 3)) fboundp hproperty:but-create vm-build-message-list vm-ml-sort-keys dont-read-attributes vm-set-default-attributes vm-read-attributes gobble-order vm-gobble-message-order vm-thread-obarray vm-build-threads vm-set-numbering-redo-start-point vm-set-summary-redo-start-point vm-summary-show-threads vm-update-summary-and-mode-line copy-sequence vm-sort-messages "thread" vm-virtual-buffers buffer-name vm-build-virtual-message-list vm-message-pointer t vm-need-summary-pointer-update vm-preview-current-message] 4> 3)

Results are similar (the same?) for other choices.

===============================================
Lynn D. Newton
Motorola Computer Group
Tempe, AZ
===============================================

