Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Didn't work for me either, hmmm' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Didn't work for me either, hmmm
Authored by: Kip on Jul 17, '03 11:37:07AM

Running 10.2.6 and Mail 1.2.5 (v552), I quit, waited a bit and then did the defaults write method of updating the preferences. Checked by doing the defaults read on the same to be sure it took.

Fired up again, looked through my unread mail to find a likely HTML candidate and it opened with the usual HTML stuff, no plain text.

Any ideas folks?

[ Reply to This | # ]
Didn't work for me either, hmmm
Authored by: poultryfarm on Jul 17, '03 02:53:31PM

didn't work for me the first few times. then i tried rob's terminal method and it now works.

i still get some html messages that display as html (perhaps the ones that have nothing but images?) but others are displayed in all text.
very nice

try it again

[ Reply to This | # ]
Didn't work for me either, hmmm
Authored by: jyncroft on Jul 17, '03 07:58:18PM

Some emails contain nothing *but* html formatted text. You should be able to type cmd-[ and cmd-] to cycle through the different parts, this is how I viewed the plain text versions before (some emails didn't have a plain text version).

HTH, Jennifer

[ Reply to This | # ]
Use different capitalization of PreferPlainText
Authored by: mesch on Aug 31, '03 09:47:15AM
The parameter names apparently are case sensitive, at least some of the time: for me it first did not work either, but prefers plain text after setting PreferPlaintext and PreferPlainText to TRUE in addition to Preferplaintext as shown above. I didn't care to figure out which one made the deal, though. 1.2.5 (v552), MacOS 10.2.6.

[ Reply to This | # ]
Beware of capitalization of highlighted search results
Authored by: mesch on Aug 31, '03 10:07:36AM
I found this hint using a search for "plain", "text" and "mail", like so: On the result page, the search words are highlighted regardless of their case. However, the highlighted words are capitalized as in the search query, not as they appear originally. Thus, on the search results page, the salient line of the hint reads defaults write Preferplaintext -bool TRUE, which wouldn't work because of case sensitivity of parameter names.

[ Reply to This | # ]