Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael R. Wolf <MichaelRWolf@att.net>
Subject: Re: Viewing MIME alternatives or raw data
Date: Wed, 12 Nov 2003 22:25:19 -0800	[thread overview]
Message-ID: <u7k24u6nk.fsf@att.net> (raw)
In-Reply-To: <m3u16it3ub.fsf@defun.localdomain>

Jesper Harder <harder@myrealbox.com> writes:

> David Z Maze <dmaze@mit.edu> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>> When a message is of type multipart/alternative, how do I change which
>>> alternative is shown ?
>>
>> You can press C-d in the summary buffer to see the structure of the
>> message, which includes alternatives for that sort of message.
>
> There's also `K b' (gnus-summary-display-buttonized) which for
> multipart/alternative allows you select which part to use:
>
>         1.  (*) text/plain          ( ) text/html           

I've just recently set this in my config so that the buttons *always*
show up.

    gnus-inhibit-mime-unbuttonizing t


It's a double-negative inhibit.*un, but when set to t, it shows the
buttons. If I don't like the html->text (which is quite often the
case), I type 'h' to get into the message buffer, 'TAB' to get over
the text/plain button, then 'CR' to see the text/plain instead of the
textualized version of text/html. It's worked very well for me.


gnus-inhibit-mime-unbuttonizing's value is t

Documentation:
If non-nil, all MIME parts get buttons.
When nil (the default value), then some MIME parts do not get buttons,
as described by the variables `gnus-buttonized-mime-types' and
`gnus-unbuttonized-mime-types'.

You can customize this variable.

Defined in `gnus-art'.

-- 
Michael R. Wolf
    All mammals learn by playing!
        MichaelRWolf@att.net


      parent reply	other threads:[~2003-11-13  6:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <jwvu16izdph.fsf-monnier+gnu.emacs.gnus@vor.iro.umontreal.ca>
     [not found] ` <?fnord?u4qyi3152.fsf@ID-97657.usr.dfncis.de>
2003-10-10 18:18   ` Ivan Boldyrev
     [not found] ` <878ynuqtc4.fsf@everett.mit.edu>
     [not found]   ` <m3u16it3ub.fsf@defun.localdomain>
2003-11-13  6:25     ` Michael R. Wolf [this message]

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=u7k24u6nk.fsf@att.net \
    --to=michaelrwolf@att.net \
    /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).