Gnus development mailing list
 help / color / mirror / Atom feed
From: david.goldberg6@verizon.net (Dave Goldberg)
To: ding@gnus.org
Subject: Re: start of art
Date: Sun, 06 Feb 2011 21:11:59 -0500	[thread overview]
Message-ID: <84d3n47fv4.fsf@davestoy.home> (raw)
In-Reply-To: <87k4hdrqoj.fsf@mat.ucm.es> (Uwe Brauer's message of "Sun, 06 Feb	2011 18:58:04 +0100")


>>> Regarding Re: start of art; Lars Ingebrigtsen <larsi@gnus.org> adds:
>> Uwe Brauer <oub@mat.ucm.es> writes:
Ted> Oh, I didn't realize Uwe was looking at the
Ted> text-plain content.  Never mind.
>>> 
>>> What is the state of art of the problem? 

>> The message is a multipart/alternative message.  You seem to be looking
>> at the text/plain version, possibly because you have discouraged HTML
>> via `mm-discouraged-alternatives', or you don't have a HTML renderer
> the value of this variable is 
> Value: ("text/html" "text/richtext" "text/enriched" "multipart/related" "image/.*")
>> (like w3m) installed.
> W3m is intalled!


> So what shall I do (I already told the gmail user to
> activate the plain text option but I don't consider this as
> a optimal solution)

Stop discouraging html?  The default for mm-discouraged-alternatives appears to be nil so you've customized it.  If you have a reason for doing so for most articles but prefer to see the html rendered on occasion you can set gnus-mime-display-multipart-alternative-as-mixed to t, which results in the article giving you buttons to switch between the alternatives; or you can just set gnus-inhibit-mime-unbuttonizing to t so you never miss a part, which is my preference.  If you do one of those and keep your setting for discouraging html, the text/plain should be shown by default, at least that's how I remember it working.  I no longer discourage html.  At work I ended up having to either switch to it or run K-H to show it in a browser for nearly every message.  But I don't want to start anothe
 r discussion of like the one going on in the top posting thread (I have to deal with that one at work too - my solution is similar to Ted's).


-- 
Dave Goldberg
david.goldberg6@verizon.net



  reply	other threads:[~2011-02-07  2:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 17:49 [Uwe Brauer] Re: test html Uwe Brauer
2011-02-04 19:04 ` Lars Ingebrigtsen
2011-02-04 21:42   ` Uwe Brauer
2011-02-04 21:50     ` Lars Ingebrigtsen
2011-02-04 22:40       ` Uwe Brauer
2011-02-05  0:19         ` Ted Zlatanov
2011-02-05  8:56           ` Uwe Brauer
2011-02-05  9:42             ` Andreas Schwab
2011-02-05 10:20               ` Uwe Brauer
2011-02-05 11:25                 ` Andreas Schwab
2011-02-05 14:01               ` Ted Zlatanov
2011-02-05 18:13                 ` start of art (was: [Uwe Brauer] Re: test html) Uwe Brauer
2011-02-05 19:03                   ` start of art Lars Ingebrigtsen
2011-02-06 17:58                     ` Uwe Brauer
2011-02-07  2:11                       ` Dave Goldberg [this message]
2011-02-07 10:24                         ` Uwe Brauer
2011-02-07 10:29                           ` Lars Ingebrigtsen
2011-02-07 17:47                             ` Uwe Brauer
2011-02-07 17:53                               ` Lars Ingebrigtsen
2011-02-08 15:05                                 ` Uwe Brauer
2011-02-14  2:45                                   ` Lars Ingebrigtsen
2011-02-05  9:08           ` [Uwe Brauer] Re: test html Uwe Brauer

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=84d3n47fv4.fsf@davestoy.home \
    --to=david.goldberg6@verizon.net \
    --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).