re-mime-type?

re-mime-type?

[Wes Hardaker]

I frequently get attachments which I know are text (like code files
ending in .c or .h) but are marked application/octet-string by the
remote side due to stupid mail agents or stupid users.  So, trying to
display it inline within gnus ('b') merely asks me for a save
location.  Is it possible to force the displaying into the article
buffer regardless of what gnus thinks it can display?  If not, I'd
think it'd be easy to add this.  Hmm...  I didn't try 'C-u b'.

-- 
"The trouble with having an open mind, of course, is that people will
 insist on coming along and trying to put things in it."   -- Terry Pratchett

Re: re-mime-type?

[Josh Huber]

Wes Hardaker <wes@hardakers.net> writes:

> I frequently get attachments which I know are text (like code files
> ending in .c or .h) but are marked application/octet-string by the
> remote side due to stupid mail agents or stupid users.  So, trying
> to display it inline within gnus ('b') merely asks me for a save
> location.  Is it possible to force the displaying into the article
> buffer regardless of what gnus thinks it can display?  If not, I'd
> think it'd be easy to add this.  Hmm...  I didn't try 'C-u b'.

How about K i

?

-- 
Josh Huber

Re: re-mime-type?

[Kai Großjohann]

Wes Hardaker <wes@hardakers.net> writes:

> I frequently get attachments which I know are text (like code files
> ending in .c or .h) but are marked application/octet-string by the
> remote side due to stupid mail agents or stupid users.

I use h to go to the article buffer, then TAB my way to the button,
then t to enter the type to view as.  (That way, you can type
application/emacs-lisp when appropriate and get font-locking.)
-- 
Ambibibentists unite!

Re: re-mime-type?

[Mark Thomas]

Wes Hardaker <wes@hardakers.net> writes:

> I frequently get attachments which I know are text (like code files
> ending in .c or .h) but are marked application/octet-string by the
> remote side due to stupid mail agents or stupid users.

I added a K t key binding to the *Summary* buffer that calls
gnus-mime-view-part-as-type.  You give it a numerical prefix to work
on a particular MIME part, and you are prompted to enter the type in
the mini-buffer.  The default type is based on the file extension, and
it works well for images.  I haven't tried with other attachment
types.

-Mark


  (defun mthomas:gnus-article-view-part-as-type (n)
    "View MIME part N as a different MIME type."
    (interactive "p")
    (gnus-article-part-wrapper n 'mthomas:gnus-mime-view-part-as-type))
  
  (defun mthomas:gnus-mime-view-part-as-type (&optional ignored)
    "gnus-article-part-wrapper--called from
  mthomas:gnus-article-view-part-as-type--gives us a handle, but
  gnus-mime-view-part-as-type doesn't use it.  This wrapper fixes the
  args that gnus-mime-view-part-as-type expects"
    (interactive)
    (gnus-mime-view-part-as-type))
  
  (defun mthomas:gnus-summary-mode-hook ()
    "A hook called from gnus-summary-prepare-hook."
    (define-key gnus-summary-mode-map [(K) (t)]
      'mthomas:gnus-article-view-part-as-type)
    ....)

Re: re-mime-type?

[Wes Hardaker]

>>>>> On Mon, 27 Jan 2003 16:27:04 -0500, Mark Thomas <swoon@bellatlantic.net> said:

Mark> I added a K t key binding to the *Summary* buffer that calls
Mark> gnus-mime-view-part-as-type.

That should probably be part of the default binding set, I think.

K i, as mentioned by Josh, would work as well in my case though.

-- 
"The trouble with having an open mind, of course, is that people will
 insist on coming along and trying to put things in it."   -- Terry Pratchett