Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Cc: ding@gnus.org
Subject: Re: finally on pgnus, but confused about MIME
Date: 01 Nov 1999 00:53:09 +0100	[thread overview]
Message-ID: <871zab140q.fsf@pc-hrvoje.srce.hr> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "31 Oct 1999 15:34:43 -0800"

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> Hrvoje> merlyn@stonehenge.com (Randal L. Schwartz) writes:
> >> How do I get at that "2." thing?
> 
> Hrvoje> Because the GIF is technically the second MIME part.  Press
> Hrvoje> `K b', and you'll understand it.  Press `K C-h' to see what
> Hrvoje> MIME commands are available.
> 
> Perhaps the manual needs to be updated to include these mysterious
> "K ... " commands. :)

I thought it was.  <check check...> You're right, they aren't in the
manual.  Well, yes, I agree they should be documented.  :-)

> Hrvoje>   (Note that the commands take numeric prefix that
> Hrvoje> corresponds to the number you see.)  Or, you can do the same
> Hrvoje> using the context-sensitive menu on button3.
> 
> I don't have a "button3".  I'm in text mode.

Then use the mysterious functions.  The mouse menu is just a nice
shortcut for when you don't feel like thinking about numbers, cryptic
bindings and stuff.

(Not that I have anything against cryptic bindings.  Cryptic bindings
are nice.  It's *new* cryptic bindings that suck.:-)

> Hrvoje> The most frequently used MIME command is `b', which
> Hrvoje> "activates" the MIME part, i.e. shows it inline, runs an
> Hrvoje> external command, whatever is appropriate.  In your case,
> Hrvoje> pressing `2 b' would display the image as dictated by your
> Hrvoje> .mailcap file.
> 
> Ahh, I guess I have to get a .mailcap file then.  Where is the
> description of that?

An example of .mailcap comes with Nathaniel Borenstein's "metamail"
package.  If you have it installed, the mailcap should be at
(/usr/local)?/etc/mailcap.

But if your MIME needs are simple (mine are), you needn't worry about
gory details.  A .mailcap entry typically looks like this:

image/gif; xv %s

That should be enough to get you started.


  reply	other threads:[~1999-10-31 23:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-31 23:22 Randal L. Schwartz
1999-10-31 23:30 ` Hrvoje Niksic
1999-10-31 23:34   ` Randal L. Schwartz
1999-10-31 23:53     ` Hrvoje Niksic [this message]
1999-11-07  0:28       ` Lars Magne Ingebrigtsen
1999-11-02  1:38     ` Per Abrahamsen
1999-11-02  9:22       ` Steinar Bang

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=871zab140q.fsf@pc-hrvoje.srce.hr \
    --to=hniksic@srce.hr \
    --cc=ding@gnus.org \
    /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).