Uploaded vm 6.68-1 (source all) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Sat, 27 Feb 1999 23:38:16 -0600
Source: vm
Binary: vm
Architecture: source all
Version: 6.68-1
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <srivasta@debian.org>
Description:
vm - A mail user agent for Emacs
Changes:
vm (6.68-1) unstable; urgency=low
.
* Added doc-base support.
* New upstream version. Please NOTE: Kyle has retracted support for emacs
20.3, saying that there is an bug in that version of emacs whence a
buffer string copy does not copy the contents of the buffer, causing
mail to be distorted. I have personally committed to using emacs20 v
20.3, and I have never experienced this bug. However, the chance does
exist (and has existed for all emacs20+vm combinations); use this on
emacs20 at your own risk. (I have changed VM so it does at least
compile on Emacs 20.3).
* Excerpted changes:
* put user specified Netscape switches before the -remote stuff
in the arg list to Netscape.
* vm-imap-retrieve-to-crashbox: use char-after instead of
char-before since Emacs 19.34 doesn't have char-before.
* use vm-coding-system-name instead of coding-system-name. fset
vm-coding-system-name to coding-system-name if it exists,
otherwise use symbol-name. FSF Emacs doesn't have a
coding system object, so the name is the same as the coding
system symbol's name.
* vm-determine-proper-charset: wrap the guts of the function in a
vm-with-multibyte-buffer form to ensure we're looking at
characters instead of the raw encoding data when scanning for
the character sets that are present.
* vm-decode-mime-layout: support the old 'name' parameter when
supporting vm-infer-mime-types.
* vm-do-reply: don't match vm-subject-ignored-prefix against the
subject to determine if we prepend vm-reply-subject-prefix to
the subject or not. This reverts a change made in VM 6.47.
* vm-mm-layout: call vm-mime-parse-entity-safe instead of
vm-mime-parse-entity so that we get always get a layout back.
This avoids a MIME part completely disappearing if we can't
parse it.
* vm-mime-parse-entity-safe: use type "error/error" for the
layout returned if the MIME part can't be parsed.
* vm-mime-qp-encode-region: hex encode _ and ? for Q encoding as
required by RFC 2047.
* vm-mime-send-body-to-file: Func-bind jka-compr-get-compression-info
to 'ignore' to avoid double compression of saved MIME bodies that
are already compressed.
* vm-imap-make-session: quote (using IMAP quoting rules) login
name and password that are sent as part of the LOGIN command.
* vm-mime-parse-entity-safe: pass message and passing-message-only
flag to vm-mime-parse-entity.
* vm-mime-parse-entity: wrong number of fields in the last layout
structure fixed.
* make MIME transfer encoding/decoding work buffers unibyte to
avoid corruption when characters are copied from them. (FSF
Emacs only).
* vm-mime-attach-message: store the message to attach in an
unibyte buffer instead of a multibyte buffer.
* vm-mime-fsfemacs-encode-composition: encode text regions using
coding system selected from vm-mime-mule-coding-to-charset-alist
instead of relying on buffer-file-coding-system to be set properly.
* vm-mime-fsfemacs-encode-composition: when handling the attachment
of a composite object, add MIME header section (if not already
provided) before parsing and transfer encoding the object.
vm-mime-xemacs-encode-composition similarly modified.
* New variables:
+ vm-mime-qp-decoder-program
+ vm-mime-qp-decoder-switches
+ vm-mime-qp-encoder-program
+ vm-mime-qp-encoder-switches
* set-file-coding-system -> set-buffer-file-coding-system.
* vm-edit-message: force edit buffer to be unibyte (FSF Emacs
only).
* vm: force folder buffer to be unibyte (FSF Emacs only).
* wrap parts of various MIME decoding and display functions in
vm-with-unibyte-buffer so we can work with unwashed 8-bit data
directly. (FSF Emacs only).
* force some buffers we create to be unibyte buffers to avoid
conflabulation of 8-bit data. (FSF Emacs only).
* vm-find-trailing-message-separator: point still not moving backward
all the times that it should be, so go back to ignoring the return
value of vm-find-leading-message-separator and always moving backward.
* vm-mail-mode-insert-message-id-maybe: use the hostname variable
we so carefullly initialized, instead of just using
(system-name).
* vm-mime-base64-encode-region: if B encoding, strip newlines from
the work buffer instead of the buffer region we're converting.
* vm-mime-base64-encode-region: don't emit status message unless
the region we're encoding is larger than 200 chars.
* vm-mime-parse-entity: new fourth argument that tells the
function whether to use the message argument for positional
information or to just use it to struct in the message slot of
the MIME layout struct. Same for vm-mime-parse-entity-safe.
Use this new argument appropriately in various places so the
message slot gets filled in more places.
Files:
b8d1dd96a13391c284d13272cdaa5504 647 mail optional vm_6.68-1.dsc
a30dad5d726a57ba8ac346765b98371e 317640 mail optional vm_6.68.orig.tar.gz
e9f9513d0d551bc6d26c73e89489eb61 44489 mail optional vm_6.68-1.diff.gz
6929185c8de21c035b3cf31712e8b32c 409746 mail optional vm_6.68-1_all.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Requires PGP version 2.6 or later.
iQCVAwUBNtjbom3FgPXHJhCVAQHgUgP/Y6VPgcRwxPNi7TclqbYiQs2lMmwxiEbz
5B3rzsXN9g0EPFVRDKZJfhcmKl7f9Twvse54zGBkAX+u8SMOWO2cCdTgTLWTQGtS
WQkHVVJk7r4uZsdKQvHWsyHhPP7viu25YvUBDYeWhuM2VqVrTjSSZbfLmjGho3gz
ve26MnEjvsg=
=kpwp
-----END PGP SIGNATURE-----
Reply to: