From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/17825 Path: main.gmane.org!not-for-mail From: Steinar Bang Newsgroups: gmane.emacs.gnus.general Subject: Re: Some MIME suggestions... Date: 14 Oct 1998 10:55:54 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: <2n90ijkc1t.fsf@zsh.cs.rochester.edu> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1035156455 2870 80.91.224.250 (20 Oct 2002 23:27:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:27:35 +0000 (UTC) Return-Path: Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id EAA05386 for ; Wed, 14 Oct 1998 04:56:29 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.7.6/8.7.3) with ESMTP id DAF07343; Wed, 14 Oct 1998 03:27:17 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 14 Oct 1998 03:56:16 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id DAA28823 for ; Wed, 14 Oct 1998 03:56:08 -0500 (CDT) Original-Received: from viffer.oslo.metis.no (viffer.oslo.metis.no [195.0.254.249]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id EAA05375 for ; Wed, 14 Oct 1998 04:55:56 -0400 (EDT) Original-Received: (from sb@localhost) by viffer.oslo.metis.no (8.8.7/8.8.7) id KAA07166; Wed, 14 Oct 1998 10:55:54 +0200 Original-To: ding@gnus.org In-Reply-To: Hrvoje Niksic's message of "14 Oct 1998 10:25:18 +0200" Original-Lines: 29 X-Mailer: Gnus v5.6.42/XEmacs 20.4 - "Emerald" Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:17825 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:17825 >>>>> Hrvoje Niksic : > Shenghuo ZHU writes: >> >>>>> "HN" == Hrvoje Niksic writes: >> HN> 2) There should be a way to force inlining an attachment. For HN> example, many people send patches as application/octet-stream; HN> I'd like to be able to press a button to force inlining the HN> patch text. Perhaps `v' over button should offer "inline" as a HN> viewer. Or something. >> >> Is `i' over button the way to force inlining an attachment? > Yes; that's exactly what I wanted, thanks. >> Suggestion: `i' with argument inlines part with selected charset. > No. `i' with an argument prompts you for MIME type. When you enter a > textual type, you can easily add `;charset=CHARSET'. Should the message be permanently changed to the new MIME type? My opinion is that it should. *If* the back end allows editing, that is. I haven't gotten around to installing pgnus yet, so I can't test it myself. Maybe today's the day? Hm... where did I put the article with the receipe for using tm-edit.el in message mode, without using TM? Hm... I don't seem to have kept it around... oh well...