Re: Can we null (or nuke) `format-alist'?

While we're on the subject of `find-file' opacities, is there a good reason not to make `format-alist' nil by default? The only things left there by default are the "image/*" formats and "text/enriched". `image-mode' is still too broken to be invoked by default, IMHO, and lives in a package now and I don't know what `format-decode' will do if it can't find its handler. "text/enriched" is nearly redundant if you're using a modern MUA like VM or Gnus, or use tm or SEMI. Maybe even dangerous, if the transformations used aren't idempotent (which they might not be in a multi-message Mule environment). Since `format-alist' is not documented anywhere that I could cross- reference from `find-file' (I only found it because I remembered that insert-file-contents-literally nulls a variable which seemed totally unconnected to `find-file', so I looked there), we should either nuke this entirely (yeah, yeah, I know, but dreams are still legal, aren't they?) or document it. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."