<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Some stuff &#187; mac os x</title>
	<atom:link href="http://blog.yhuang.org/?feed=rss2&#038;tag=mac-os-x" rel="self" type="application/rss+xml" />
	<link>https://blog.yhuang.org</link>
	<description>here.</description>
	<lastBuildDate>Wed, 27 Aug 2025 08:50:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>Disable Apple Mail attachment defaulting to inline</title>
		<link>https://blog.yhuang.org/?p=1642</link>
		<comments>https://blog.yhuang.org/?p=1642#comments</comments>
		<pubDate>Fri, 13 Nov 2015 01:19:50 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Address Book]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[command line]]></category>
		<category><![CDATA[Graphical user interface]]></category>
		<category><![CDATA[IPhone OS]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[Macintosh]]></category>
		<category><![CDATA[MobileMe]]></category>
		<category><![CDATA[Operating system]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[plain text]]></category>
		<category><![CDATA[Unix]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://scripts.mit.edu/~zong/wpress/?p=1642</guid>
		<description><![CDATA[Did you know that Apple Mail does the presumptuous thing of sending all images (and maybe other attachment types) as inline attachments, no matter what options you choose in the program, like attaching at the end of message, like making it &#8220;Windows-friendly&#8221; (as if it&#8217;s a Windows problem),&#8230;. Nor does any of the very typically [...]]]></description>
			<content:encoded><![CDATA[<p>Did you know that Apple Mail does the presumptuous thing of sending all images (and maybe other attachment types) as inline attachments, no matter what options you choose in the program, like attaching at the end of message, like making it &#8220;Windows-friendly&#8221; (as if it&#8217;s a Windows problem),&#8230;. Nor does any of the very typically low-quality &#8220;solutions&#8221; you&#8217;ll find by misunderstanding Apple users online help, like changing message type to plain text or running that one silly line on the command line</p>
<blockquote><p>defaults write com.apple.mail DisableInlineAttachmentViewing -bool yes</p></blockquote>
<p>Just look at that and think about what it does! None of those do anything at all.<br />
<span id="more-1642"></span><br />
But I found this today after much searching: <a href="http://clivegaleni.com/posts/os-x-mail-disable-inline-attachments/">OS X Mail &#8211; disable inline attachments</a>, and it is indeed the only solution that works.</p>
<p><em>Edit:</em> However, I can no longer recommend this Mail plug-in. Not only does it nag-screen for payment an hour or so after first using it, there is not even a way to uninstall it without manually going through the system. Given how difficult it is to cleanly remove .pkg installations on OS X, I consider this thing to be in terrible taste. Use at your own risk.</p>
]]></content:encoded>
			<wfw:commentRss>https://blog.yhuang.org/?feed=rss2&#038;p=1642</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>user input should take absolute precedence</title>
		<link>https://blog.yhuang.org/?p=719</link>
		<comments>https://blog.yhuang.org/?p=719#comments</comments>
		<pubDate>Fri, 11 Nov 2011 03:25:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[computing resources]]></category>
		<category><![CDATA[cpu problems]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[other crap]]></category>
		<category><![CDATA[precedence]]></category>

		<guid isPermaLink="false">http://scripts.mit.edu/~zong/wpress/?p=719</guid>
		<description><![CDATA[These and other silly &#8220;100% CPU&#8221; problems should not happen, first of all: 1. Mac OS X doesn&#8217;t know how to stop looping the CrashReporter process on repeated crashing apps. 2. 64-bit Linux kernel doesn&#8217;t know how to deal with full swap situation. But more importantly, given that &#8220;100% CPU&#8221; situations will arise, why are [...]]]></description>
			<content:encoded><![CDATA[<p>These and other silly &#8220;100% CPU&#8221; problems should not happen, first of all:</p>
<p>1. <a href="https://discussions.apple.com/thread/2417645?start=0&#038;tstart=0">Mac OS X doesn&#8217;t know how to stop looping the CrashReporter process on repeated crashing apps</a>.<br />
2. <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356">64-bit Linux kernel doesn&#8217;t know how to deal with full swap situation</a>.</p>
<p>But more importantly, given that &#8220;100% CPU&#8221; situations will arise, why are OS&#8217;s designed in such a way that basic user inputs like mouse and keyboard aren&#8217;t given precedence at all times? Even just to catch some escape key combo to give the user a chance to correct the offending situation? I don&#8217;t believe for a moment that a small amount of computing time cannot be devoted solely to process user input <em>at all times</em>. If your computing resources cannot handle that, then cut out the other crap that&#8217;s going on. If the user wants to do something, listen to the user! Simple concept.</p>
]]></content:encoded>
			<wfw:commentRss>https://blog.yhuang.org/?feed=rss2&#038;p=719</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>lessons from the PC era</title>
		<link>https://blog.yhuang.org/?p=633</link>
		<comments>https://blog.yhuang.org/?p=633#comments</comments>
		<pubDate>Sun, 28 Aug 2011 17:18:25 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[computing]]></category>
		<category><![CDATA[enterprise]]></category>
		<category><![CDATA[era]]></category>
		<category><![CDATA[history of the pc]]></category>
		<category><![CDATA[hobby]]></category>
		<category><![CDATA[mac os x]]></category>
		<category><![CDATA[mid 1980s]]></category>
		<category><![CDATA[trend]]></category>
		<category><![CDATA[usage scenarios]]></category>
		<category><![CDATA[workstation companies]]></category>

		<guid isPermaLink="false">http://scripts.mit.edu/~zong/wpress/?p=633</guid>
		<description><![CDATA[It&#8217;s interesting to consider the history of the PC and learn some lessons. The landscape of computing that we have now resulted from a sandwiching effect of cheaper and cheaper scientific workstations and more and more powerful consumer hobby kits (some say toys). By the mid 1980s, this trend was recognized and efforts were begun [...]]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s interesting to consider the history of the PC and learn some lessons. The landscape of computing that we have now resulted from a sandwiching effect of cheaper and cheaper scientific workstations and more and more powerful consumer hobby kits (some say toys). By the mid 1980s, this trend was recognized and efforts were begun from both sides to capture the computing market. Today we know that the hobby kit lineage won, and as a result, most workstation companies eventually folded in the 2000s, though they survived for a while by clinging to the enterprise. (Incidently, IBM and HP did not, because they were large and diversified enough to do something about it.)</p>
<p>But this is not the whole story.<br />
<span id="more-633"></span><br />
Look at how hobby kits finally became respectable: not with the ad-hoc hacked-up first iteration legacy which resulted in a 20-year detour through DOS/Windows 3.0, Apple II/Macintosh. People often say that the PC revolution began in 1975, but all the systems commonly used today do not go back that far, they trace back to <em>de novo</em> R&#038;D from the late 1980s / early 1990s that attempted to emulate workstations rather than make toys. Besides NeXTstep, which became Mac OS X, there was NT OS/2, which later became Windows 2000. Even GNU/Linux, which is the most UNIX like of all, came out with its first distribution in 1993. This is remarkable. It means that toys could take over the world, but cheap hardware alone was not enough, blindly ported software wasn&#8217;t enough, hacked together software wasn&#8217;t enough, it had to be well-engineered software made specifically for the device and its new usage scenarios &#8212; something that wouldn&#8217;t have been known until people played long enough with the toys.</p>
<p>So today, we have mobile devices that are still consumer toys for the most part. But like an old movie, the gap between mobile devices and PC&#8217;s is closing; the case for PC&#8217;s and PC companies is increasingly enterprise customers; and attempts to shove a downgraded PC directly into a mobile form factor like Blackberry/Windows PDA&#8217;s and netbooks are not working as well as making toys more powerful. Some things don&#8217;t change. New usages like electronic payment, geolocation, and image search are clearly emerging from the toys, and there will be a second iteration of development that make mobile devices seriously useful. It won&#8217;t be through making them do all the things that can be done <em>now</em> on the PC though &#8212; that would be impossible &#8212; it will be through making them do things that make things now done on the PC obsolete, because there will be better ways. The next ten years should be interesting.</p>
]]></content:encoded>
			<wfw:commentRss>https://blog.yhuang.org/?feed=rss2&#038;p=633</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
