From: Karl Kleinpaste <karl@justresearch.com>
Subject: [patch] mm-uu-dissect's disposition choice should be selectable
Date: 22 Dec 1998 11:22:01 -0500 [thread overview]
Message-ID: <vxkbtkwuoye.fsf@beaver.jprc.com> (raw)
Prior to p0.66, mm-uu-dissect had a hard-coded disposition of
"attachment," which I preferred, because I often want to mark a set
of articles with `#' and then do something to them without display
such as `X U'. In p0.66, this hard-coded disposition was changed to
"inline," which is (for me) a major waste of CPU and time because I
don't want the contents displayed, I just want them decoded. I can
understand why a default of "inline" would be wanted, but it ought to
be selectable.
Unfortunately, it doesn't appear that anything in mm-*.el uses
defcustom, so I just added a configurable setting with defvar.
1998-12-22 Karl Kleinpaste <karl@justresearch.com>
* mm-uu.el (mm-dissect-disposition): New variable.
(mm-uu-dissect): Use it.
--- mm-uu.el.~1~ Tue Dec 15 12:31:53 1998
+++ mm-uu.el Tue Dec 22 11:13:38 1998
@@ -68,6 +68,8 @@
(defvar mm-uu-identifier-alist
'((?% . postscript) (?b . uu) (?: . binhex) (?# . shar)))
+(defvar mm-dissect-disposition "inline")
+
;;;### autoload
(defun mm-uu-dissect ()
@@ -135,7 +137,7 @@
"application/octet-stream"))
mm-uu-decode-function nil
(if (and file-name (not (equal file-name "")))
- (list "inline" (cons 'filename file-name)))))
+ (list mm-dissect-disposition (cons 'filename file-name)))))
((eq type 'binhex)
(mm-make-handle (mm-uu-copy-to-buffer start-char end-char)
(list (or (and file-name
@@ -145,7 +147,7 @@
"application/octet-stream"))
mm-uu-binhex-decode-function nil
(if (and file-name (not (equal file-name "")))
- (list "inline" (cons 'filename file-name)))))
+ (list mm-dissect-disposition (cons 'filename file-name)))))
((eq type 'shar)
(mm-make-handle (mm-uu-copy-to-buffer start-char end-char)
'("application/x-shar"))))
reply other threads:[~1998-12-22 16:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=vxkbtkwuoye.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/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).