<?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>heipei's weblog &#187; Apple</title>
	<atom:link href="http://heipei.net/category/apple/feed/" rel="self" type="application/rss+xml" />
	<link>http://heipei.net</link>
	<description>Johannes 'heipei' Gilger</description>
	<lastBuildDate>Sun, 01 Apr 2012 16:47:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Mops-Passwörter speichern unter Mac OS 10.6</title>
		<link>http://heipei.net/2009/12/06/mops-passworter-speichern-unter-mac-os-10-6/</link>
		<comments>http://heipei.net/2009/12/06/mops-passworter-speichern-unter-mac-os-10-6/#comments</comments>
		<pubDate>Sun, 06 Dec 2009 10:25:35 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Aachen]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>
		<category><![CDATA[Uni]]></category>

		<guid isPermaLink="false">http://heipei.net/?p=727</guid>
		<description><![CDATA[Manchmal muss man, trotz eduroam, noch das alte Cisco-VPN benutzen um sich ins Uni-Netz einzuwählen. Z.B. wenn man von Zuhause auf Dinge wie Springerlink oder andere Online-Bibliotheken zugreifen will, oder um auf bestimmte Hosts per SSH zu kommen die (sinnvollerweise) von aussen nicht erreichbar sind. In Mac OS 10.6 Snow Leopard kann man Cisco-Verbindungen glücklicherweise [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://heipei.net/weblog/eduroam.gif" class="alignleft" alt="eduroam"/>Manchmal muss man, trotz eduroam, noch das alte Cisco-VPN benutzen um sich ins Uni-Netz einzuwählen. Z.B. wenn man von Zuhause auf Dinge wie Springerlink oder andere Online-Bibliotheken zugreifen will, oder um auf bestimmte Hosts per SSH zu kommen die (sinnvollerweise) von aussen nicht erreichbar sind.<br />
In Mac OS 10.6 Snow Leopard kann man Cisco-Verbindungen glücklicherweise direkt mit dem Betriebssystem machen und ist endlich frei von dem nervigen Cisco-Client. Allerdings hat das ganze noch einen kleinen Bug, nämlich dass man sein Passwort bei jedem Verbindungsversuch neu eingeben muss. Wie man das vermeidet steht hier: <a href="http://www.macosxhints.com/article.php?story=2009082703155512">10.6: Save Cisco IPSec password in the keychain</a></p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2009/12/06/mops-passworter-speichern-unter-mac-os-10-6/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>GitX 0.7 &#8211; Visual changelog</title>
		<link>http://heipei.net/2009/09/07/gitx-0-7-released/</link>
		<comments>http://heipei.net/2009/09/07/gitx-0-7-released/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 20:00:07 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>
		<category><![CDATA[git]]></category>

		<guid isPermaLink="false">http://heipei.net/?p=573</guid>
		<description><![CDATA[GitX 0.7 was just released today. This is the latest release since 0.6.3 and the first real feature release for some time, although we don&#8217;t make that distinction to strictly. After the jump I&#8217;ll outline the cool new features and how to make use of them. GitX mailing-list We&#8217;ve been using our Lighthouse tracker to [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/weblog/gitx_logo.png" alt="GitX 0.7" class="alignleft"/><a href="http://gitx.frim.nl/">GitX 0.7</a> was just released today. This is the latest release since 0.6.3 and the first real feature release for some time, although we don&#8217;t make that distinction to strictly. After the jump I&#8217;ll outline the cool new features and how to make use of them.</p>
<h4>GitX mailing-list</h4>
<p>We&#8217;ve been using <a href="http://gitx.lighthouseapp.com/projects/17830-gitx/overview">our Lighthouse tracker</a> to respond to bugs and to discuss features for quite a while now. Email exchanges between Pieter and other contributors were getting more common, so we decided to open a <a href="http://googlegroups.com/group/gitx/">mailing-list for GitX</a>. We already got some nice patches through the list, which has the great advantage that patches can easily be reviewed inline and discussed. The use of the GitHub-wiki is discouraged, as is the Pull-request functionality.</p>
<h4>GitX survey</h4>
<p><a href="http://www.survs.com/survey?id=DCJKLP2B&#038;channel=E965G53EBB"><img src="/weblog/survs.jpg" alt="GitX survey" class="alignright" style="margin-top: -15px; border:0px;"/></a>To accompany this release, and to improve the input from our users, we have created a small (&lt; 5 min) survey for GitX. We&#8217;d be happy if you took the time to go through it. Link to the <a href="http://www.survs.com/survey?id=DCJKLP2B&#038;channel=E965G53EBB">GitX user survey</a></p>
<p>The juicy details after the jump:<br />
<span id="more-573"></span></p>
<h4>Operations on hunks/lines</h4>
<p><img src="/weblog/gitx_0.7_discard_hunk.png" alt="GitX" class="alignleft"/>Staging and unstaging hunks has been possible for some time. What&#8217;s new is the &#8220;Discard Hunk&#8221; button which simply gets rid of that change, i.e. uses apply &#8211;reverse. As usual, the warning-box that shows up can be silenced by Alt-Clicking the button.<br />
<img src="/weblog/gitx_0.7_stagelines.png" alt="GitX 0.7" class="aligncenter"/>The most obvious change is the ability to stage specific lines from a hunk, using the left mouse-button to drag-select a few lines and then hit &#8220;Stage lines&#8221;. This is by far the most advanced method to stage stuff in a git-gui up until now.</p>
<h4>History</h4>
<p>Two small changes that should make life easier are the orange color for you current branch in the rev-list and the menu-title, which displays your current HEAD as well.<img src="/weblog/gitx_0.7_head.png" alt="GitX" class="aligncenter"/><br />
The panes which hold the list of commits and the individual diffs can now be collapsed/uncollapsed using double-click or the keystroke &#8220;Command-Shift-Up/Down&#8221;. This gives you the ability to quickly maximize complicated history or diffs.</p>
<h4>Committing</h4>
<p><img src="/weblog/gitx_0.7_commit_info.png" alt="GitX" class="alignleft"/>The commit-view gained a &#8220;Sign-Off&#8221; button. Commits keep their author information when amending. And the (Un)staged-changes list gained a &#8220;Show in Finder&#8221; menu item. The diff now shows the committer, who can be someone other than the author of a patch. Commit-hooks now get executed upon committing.</p>
<h4>General</h4>
<p>A small preference called &#8220;Show white-space differences&#8221; shows you diffs with white-space-only changes. We also tried to make most of the alert-messages run non-modal, which means they won&#8217;t block other instances of GitX. The tree-view doesn&#8217;t try to display the content of binary-files anymore. Furthermore we updated a few passages of the UserManual to reflect the current state of GitX.</p>
<h4>Bugfixes</h4>
<p>The big heap of stuff were bugfixes, some trivial, very few regressions, some simply annoying and some features to protect users from doing harm to themselves. A few of those fixes were performance-related, and with the new Safari 4 the diff-view should suffer less.</p>
<h4>What&#8217;s in the pipeline for GitX 0.8</h4>
<p>One of the changes that almost made it to GitX 0.7 is the auto-refresh feature, which monitors the repository and reloads GitX automatically when something is changed. We&#8217;re confident that this feature will be in 0.8, if not earlier.</p>
<h4>Diffstat/shortlog</h4>
<p>Shortlog:</p>
<pre>Benjamin Kramer (9):
      HistoryView: Factor out email formatting
      HistoryView: Show committer if his name differs from the author's
      HistoryView: Show commit date
      HistoryView: Make table header large enough so the text doesn't shift
      Don't compile plain ObjC files as ObjC++
      Get rid of some unnecessary casts
      Remove a .DS_Store
      Fix an obvious typo
      Fix checkbox scaling warnings

Benoit Cerrina (1):
      PBGitRepository: Fix opening of large directories due to bug in NSFileWrapper.

Charles O'Rourke (2):
      Ticket #142: Add Show in Finder to Unstaged and Staged table views.
      Tickets #151 and #155: check for illegal branch names before creating.

Gerd Knops (1):
      Fix build with external build products directory

JD Smith (4):
      commit view: Ensure buttons display on top of text ... but beneath title line.
      diffHighlighter.js: Record the line index as attribute.
      commit.js: Refactor hunk retrieval. To work with subhunks, allow passing a header line explicitly to search for.
      commit.js: Interface for selecting lines to (un-)stage.

Joe Fiorini (3):
      Write commit message to file
      Enable arguments to be passed to executeHook.
      Trigger commit-msg hook when committing

Johannes Gilger (31):
      GitX: Make toolbar in history and commit view equal height
      Info.plist: Fix handling of directories
      PBGitCommit: Call git show with --no-color to be safe
      PBGitRepository: Display branch-name in window title
      PBGitRepository: Correctly indicate bare/non-bare repos
      history.js: Fix display of mode-change and rename
      PBGitCommitController: Fix unstaging of files
      PBWebChanges: Allow discarding of hunks
      PBGitRepository: Add method to remove branch
      PBGitWindowController: Use beginSheetModalForWindow instead of runModal
      keyboardNavigation: Fix keys 'c' and 'v' from webView
      PBGitCommit: Add "Sign-Off" button/method
      PBGitCommitController: Don't allow duplicate Sign-Offs
      PBGitHistory: Add "Show in Finder" to files
      PBGitIndexController: Renamed "Revert" to "Discard"
      Add PBCollapsibleSplitView as subclass of PBNiceSplitView
      PBCollapsibleSplitView: Enable collapse/uncollapse using keys
      Statusbar: Bring View-Mode buttons to front
      Keep window-title up-to-date in commit view
      commit.js: Fix discardHunk functionality
      This fixes a CSS-bug which makes the gitx-website display the same font with Firefox and Safari instead of using a serif with FF.
      Add empty line at end of previous release notes
      UserManual: Add disclaimer as to what GitX is
      GitX 0.7 Release-Notes
      UserManual: Add disclaimer as to what GitX is
      UserManual: Rewrite most parts for GitX 0.7
      About-Panel: Show git-describe using Info.plist
      Site: W3C-Valid and CSS/HTML corrections
      ReleaseNotes for v0.7 with author information
      Site: Get rid of auto-refresh description
      PBGitTree: Don't try to print binary-file contents

Mike Czepiel (1):
      Added very basic tag info menu item and alert.

Nicholas Riley (6):
      Reduce font size of staged/unstaged changes lists.
      Don't disturb editing state when inserting "Signed-off-by" line.
      Remove extraneous space in "Are you sure you wish to revert changes?" message.
      Set keyboard focus reasonably when switching between views.
      Clean up UI and add keyboard support for create branch sheet.
      Truncate the middle of pathnames in the Unstaged/Staged Changes lists.

Pieter de Bie (51):
      Update diffHighlighter test
      HistoryView: speed up diff display
      Allow executing of hooks
      Trigger pre and post-commit hooks when committing
      CommitController: Don't rewrap commit message when amending
      Allow a user to select which columns to display
      HistoryView: Autosave column information
      GitRevList: fix crash when loading 0 commits
      GitRevList -- Try to read the encoding of the commit message
      GitRevList: cache the values of string encodings
      GitRevList: Use std::map.find() rather than count()
      GitCommitController: clean up index functions
      CommitController: Use a dictionary lookup when refreshing index
      GitCommitController: Also use dictionary lookup for untracked files
      PBChangedFile: remove shouldBeDeleted boolean
      Rename 'CachedChanges" to "StagedChanges" for greater consistency
      Add an example of how drag-selection for staging lines could work.
      HistoryView: Resize the detail webview
      Site: add link to Twitter
      PBEasyPipe: Add method that allows you to specify the environment stuff
      PBGitRepository: Specify environment when calling hooks
      PBGitRepository: Add support for changing the environment when executing commands
      NSSTring_RegEx: Add support for regular expressions to NSString
      PBGitCommitController: retain author information of previous commit
      Preferences: Resize views
      Add preference to ignore whitespace differences in history view
      CommitController: don't mutate array we enumerate when refreshing index
      HistoryView: only add parents if parents array exists
      Site: update links to reflect move to mailing list
      Remove use of deprecated stringWithCString
      PBGitConfig: Add missing sentinel
      CommitController: Notify observers when adding files
      History fileview: select current item on rightclick
      Display context menu in the history tree to show related commits
      HistoryController: Add some marks
      WebHistoryController: Refactor menu search to be recursive
      HistoryController: Use a programatically created context menu
      WebHistoryView: Also use the tree context menu
      HistoryController: Add "Open Files" menu item
      CommitController: Reject merges
      PBGitRepository: Clean up the readFromURL: method
      CommitController: Don't turn of off automatic rearranging
      Site: smush.it images
      Also set blobMode / blobSha for unstaged changes.
      PBChangedFile: Add assert to make sure we're not doing something stupid
      IndexController: re-add ellipsis to "Discard Changes" menu item
      DiffHighlighter: Remove weird end line
      HistoryView: Add "SHA" Column and make it hidden by default
      Update releasenotes, as autorefresh won't make it into 0.7
      Add a few more release points
      Add a link to the user survey

Steven Michalske (1):
      HistoryView: Change the way the HEAD is displayed

Stonewall Ballard (1):
      Add preferences for opening things at launch.

dbr (1):
      When selecting a folder in tree-view, display the path rather than the &lt;PBGitTree: 0x...&gt; object.
</pre>
<p>The shortstat has this to say:</p>
<pre>
 84 files changed, 5474 insertions(+), 1470 deletions(-)
</pre>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2009/09/07/gitx-0-7-released/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Xcode: &#8220;git describe&#8221; in your app &#8211; again</title>
		<link>http://heipei.net/2009/09/07/xcode-git-describe-in-your-app-again/</link>
		<comments>http://heipei.net/2009/09/07/xcode-git-describe-in-your-app-again/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 10:21:25 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>
		<category><![CDATA[git]]></category>

		<guid isPermaLink="false">http://heipei.net/?p=654</guid>
		<description><![CDATA[A while back I wrote about having the output of &#8220;git describe&#8221; as your version-string in your Mac-OS app, only to discover that this doesn&#8217;t work that well since the string in the Info.plist is supposed to be an constantly increasing number of the form x.y.z.zzzz, which doesn&#8217;t really work with the SHAs git gives [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/weblog/gitx-about.png" alt="GitX" class="alignleft"/>A while back <a href="http://heipei.net/2009/02/23/xcode-git-describe-in-your-infoplist/">I wrote about having the output of &#8220;git describe&#8221; as your version-string</a> in your Mac-OS app, only to discover that this doesn&#8217;t work that well since the string in the Info.plist is supposed to be an constantly increasing number of the form x.y.z.zzzz, which doesn&#8217;t really work with the SHAs git gives you. But since I really wanted that feature I kept searching and found a solution which seems to work pretty well and doesn&#8217;t interfere with the version-string.</p>
<p><b>Introducing a new key to Info.plist</b><br />
First of you&#8217;ll need an additional key in your Info.plist where your custom version-string will be stored. I used &#8220;CFBundleGitVersion&#8221; and set its content to &#8220;GIT_VERSION&#8221;. You can simply do that in XCode.</p>
<p><b>The build-script</b><br />
You&#8217;ll still need a build-script, <a href="http://heipei.net/2009/02/23/xcode-git-describe-in-your-infoplist/">like I described before</a>. A really simple one would be:<br />
<code>VERSION=$(cd $PROJECT_DIR; git describe)<br />
echo -n "#define GIT_VERSION $VERSION" > $PROJECT_TEMP_DIR/revision<br />
touch Info.plist</code>If that doesn&#8217;t work you might need to include some PATH exports above, but I wanted to keep this example to the relevant parts.</p>
<p><b>Info.plist preprocessing</b><br />
Now you can preprocess the Info.plist when building your app, using the revision-file as a header. This means that your GIT_VERSION string will be replaced. Edit your Build-Settings like this:<img src="/weblog/gitx-info-plist-prep.png" alt="Info.plist preprocessing using git describe" class="aligncenter"/><br />
<b>Using the string in the About-window</b><br />
So, now your Info.plist contains a meaningful string. You want that to be displayed to the user when he opens the &#8220;About&#8221; window, but you don&#8217;t want to write your own window. First you have to write an IBAction in some controller that&#8217;s in your MainMenu.xib. Then you&#8217;ll have to reconnect the About-button to that action from your controller, which should look like this:</p>
<pre>- (IBAction)showAboutPanel:(id)sender
{
	NSString *gitversion = [[[NSBundle mainBundle] infoDictionary]
		objectForKey:@"CFBundleGitVersion"];
	NSMutableDictionary *dict = nil;
	if (gitversion)
		dict = [[NSMutableDictionary alloc] initWithObjectsAndKeys:
			gitversion, @"Version", nil];

	[NSApp orderFrontStandardAboutPanelWithOptions:dict];
}</pre>
<p>So, if gitversion is set then the default Version-string is overwritten with it when calling the about-panel, while for Mac-OS the extra-key in your Info.plist is completely meaningless and to differentiate between version you can still use a simple integer. If that was to hard to follow just have a look <a href="http://github.com/pieter/gitx/commit/0b81911d76a819fea58d7c1aba98302cb8703d70">at the commit in the GitX-repo</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2009/09/07/xcode-git-describe-in-your-app-again/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Xcode: git describe in your Info.plist</title>
		<link>http://heipei.net/2009/02/23/xcode-git-describe-in-your-infoplist/</link>
		<comments>http://heipei.net/2009/02/23/xcode-git-describe-in-your-infoplist/#comments</comments>
		<pubDate>Mon, 23 Feb 2009 11:50:41 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Allgemein]]></category>
		<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>
		<category><![CDATA[git]]></category>

		<guid isPermaLink="false">http://hackvalue.de/heipei/?p=421</guid>
		<description><![CDATA[Debugging programs for yourself (or from bug-reports from other people) requires knowing which version caused the bug. Of course most people think in terms of major releases, but a developer needs to know the exact revision, as this might make the crucial difference. UNIX command-line programs usually offer a &#8211;version switch, which returns detailed version [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/heipei/weblog/xcode_git_describe.png" alt="Xcode git describe" class="alignleft"/>Debugging programs for yourself (or from bug-reports from other people) requires knowing which version caused the bug. Of course most people think in terms of major releases, but a developer needs to know the exact revision, as this might make the crucial difference. UNIX command-line programs usually offer a &#8211;version switch, which returns detailed version and build-option information.</p>
<p>If you want to have something similar with Xcode you can use the &#8220;New Run Script Build Phase&#8221; to add a simple script to your build-process. In the case of GitX, the code looks like this (the original can be found at <a href="http://github.com/indirect/xcode-git-build-scripts/tree/master">xcode-git-build-scripts at GitHub</a>):</p>
<pre>#!/usr/bin/env ruby

version = `/usr/bin/env git describe`.chomp

info_file = File.join(ENV['BUILT_PRODUCTS_DIR'], ENV['INFOPLIST_PATH'])
info = File.open(info_file, "r").read

version_re = /([t ]+&lt;key&gt;CFBundleVersion&lt;/key&gt;n[t ]+&lt;string&gt;).*?(&lt;/string&gt;)/
info =~ version_re
bundle_version_string = $1 + version + $2

info.gsub!(version_re, bundle_version_string)
File.open(info_file, "w") { |file| file.write(info) }
puts "Set version string to '#{version}'"
</pre>
<p>Needless to say that this script is not very error-resistant, but since ruby is included with OSX and people compiling GitX usually have git installed, it should work in most cases.<br />
<b>Update</b><br />
I just discovered that the CFBundVersion is supposed to be a monotically increasing integer, separated only by periods. This is required by MacOS and things like Sparkle. The string &#8220;git describe&#8221; returns doesn&#8217;t match these criteria, obviously. So, if you encounter problems, you should fall back to using the format of x.y.z.&lt;commits&gt; where x.y.z is your major release number and &lt;commits&gt; is the number of commits since mentioned tag.</p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2009/02/23/xcode-git-describe-in-your-infoplist/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>MacOS X: GeekTool &amp; SSID/BSSID from Terminal</title>
		<link>http://heipei.net/2009/02/08/macos-x-geektool-ssidbssid-from-terminal/</link>
		<comments>http://heipei.net/2009/02/08/macos-x-geektool-ssidbssid-from-terminal/#comments</comments>
		<pubDate>Sun, 08 Feb 2009 11:54:52 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>

		<guid isPermaLink="false">http://hackvalue.de/heipei/?p=414</guid>
		<description><![CDATA[Working on my laptop a little bit more since I bought myself a new one I began the never-ending quest of doing things in MacOS via command-line that you&#8217;d have to do by GUI otherwise. But let me start by introducing GeekTool, a funny little PrefPane to display the output of commands on your desktop. [...]]]></description>
			<content:encoded><![CDATA[<p>Working on my laptop a little bit more since I bought myself a new one I began the never-ending quest of doing things in MacOS via command-line that you&#8217;d have to do by GUI otherwise. But let me start by introducing <a href="http://projects.tynsoe.org/en/geektool/">GeekTool, a funny little PrefPane</a> to display the output of commands on your desktop. Mine looks like this right now:<br />
<a href="http://www.flickr.com/photos/heipei/3260073285/" title="GeekTool by heipei, on Flickr"><img src="http://farm4.static.flickr.com/3497/3260073285_9a51ddff9a.jpg" width="500" height="313" alt="GeekTool" class="aligncenter" /></a>Most of the information there is redundant or meaningless. But two things I do care about: The SSID and BSSID (MAC-address) of the access-point I&#8217;m currently connected with. To get that info via the GUI you can Alt-Click the Airport-logo in the menubar, but you can also query it via commandline:<br />
SSID: <code>/usr/sbin/system_profiler SPAirPortDataType|grep "Current Wireless Network"</code>BSSID: <code>/System/Library/PrivateFrameworks/Apple80211. framework/Versions/A/Resources/airport -I|grep BSSID</code><br />
In case you&#8217;re wondering: I have a wireless network at home with two APs, and sometimes I want to know which one I&#8217;m connected to, to see which one is causing trouble and to generally watch how the two signals propagate through the building.<br />
<b>Update</b><br />
Hey, even better than just bitching about being on the &#8220;wrong&#8221; AP is manually changing to a different BSSID:<br />
<code>./airport -z<br />
./airport --associate="heipei" --bssid="00:00:00:00:00:00" --password="supersecret"</code></p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2009/02/08/macos-x-geektool-ssidbssid-from-terminal/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Unison &#8211; Stay in sync</title>
		<link>http://heipei.net/2008/12/03/unison-stay-in-sync/</link>
		<comments>http://heipei.net/2008/12/03/unison-stay-in-sync/#comments</comments>
		<pubDate>Tue, 02 Dec 2008 22:06:32 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>
		<category><![CDATA[Gentoo]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://hackvalue.de/heipei/?p=371</guid>
		<description><![CDATA[I use git to version almost everything I work with on a daily basis. My emails reside on an IMAP-server and my bookmarks are on delicious. My config files are written such that the same file can be used on any machine I have. The question remains how to keep all of the other stuff [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/heipei/weblog/unison.gif" alt="Unison" class="alignleft"/>I use git to version almost everything I work with on a daily basis. My emails reside on an IMAP-server and my bookmarks are on delicious. My config files are written such that the same file can be used on any machine I have. The question remains how to keep all of the other stuff in sync.<br />
There are excellent backup-solutions (and you can easily write your own), there&#8217;s git for version-control and of course there is rsync, but often you wan&#8217;t something else. Obviously you don&#8217;t want to put big files that can&#8217;t be efficiently compressed into a git repo (making it twice as big) and then push/pull multiple repos everytime you changed one file on one host. rsync also has a few drawbacks.<br />
Enter Unison. Unison can best be described as a bi-directional rsync with a nice GUI which can be started from one host. The problem with just using rsync is that when you sync you effectively designate one host as master and the other one as the one that should be overwritten if needed. The user interface leaves much to be desired as well. I use rsync mostly for unsupervised backups.<br />
<img src="/heipei/weblog/unison_macos.png" alt="Unison" class="aligncenter"/><br />
Unison solves all of these problems. It works with profiles, where local and remote paths are specified and ignore masks can be set. Then when started on a profile it checks the paths, and gives you pretty good settings to sync it (obviously if a file is changed you probably want the newer one on both hosts, and if a file was deleted but was there before, you probably want to delete it on the other host as well). You can then go through the file list and use keyboard shortcuts to mark files as use-local, use-remote, skip for this sync and ignore permanently. It may not sound that spectacular, but that is exactly what sets Unison apart. So, if you work on more than one host give it a try, it works on Windows, Linux and Mac OS X.</p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2008/12/03/unison-stay-in-sync/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>viminfo with Mac OS X</title>
		<link>http://heipei.net/2008/10/30/viminfo-with-mac-os-x/</link>
		<comments>http://heipei.net/2008/10/30/viminfo-with-mac-os-x/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 12:21:44 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>

		<guid isPermaLink="false">http://hackvalue.de/heipei/?p=341</guid>
		<description><![CDATA[Finally, I found a solution to something that has really been bugging me for quite some time. I use vim, not only on my linux machine but also everywhere else I&#8217;m able to get my hands on it. Vim has a feature called viminfo, which is basically just a file that remembers stuff like your [...]]]></description>
			<content:encoded><![CDATA[<p><img src="/heipei/weblog/vim_logo.png" alt="Vim" class="alignleft"/>Finally, I found a solution to something that has really been bugging me for quite some time. I use vim, not only on my linux machine but also everywhere else I&#8217;m able to get my hands on it. Vim has a feature called viminfo, which is basically just a file that remembers stuff like your last edited files, the last commands, searches, etc you typed, your buffers and also, this is the important part, the position for each file you were editing when you closed it. And this feature simply did not work under Mac OS X, driving me nearly crazy. Anyway, with this little snippet in your .vimrc it should work. Enjoy.<br />
<code>if has("autocmd")<br />
    autocmd BufReadPost *<br />
	\ if line("'\"") > 0 &amp;&amp; line("'\"") &lt; = line("$") |<br />
	\ exe "normal g`\"" |<br />
	\ endif<br />
endif</code></p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2008/10/30/viminfo-with-mac-os-x/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Macbook review</title>
		<link>http://heipei.net/2008/10/26/macbook-review/</link>
		<comments>http://heipei.net/2008/10/26/macbook-review/#comments</comments>
		<pubDate>Sun, 26 Oct 2008 18:34:03 +0000</pubDate>
		<dc:creator>Jojo</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Geekstuff]]></category>

		<guid isPermaLink="false">http://hackvalue.de/heipei/?p=331</guid>
		<description><![CDATA[In a shameless attempt to attract traffic I&#8217;m gonna do a short review of my new Macbook ;). I had been playing with the thought of buying a new laptop for a while now, and was almost certain it would be the Dell XPS 1330, since Apple didn&#8217;t really offer anything for me at that [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.flickr.com/photos/heipei/2965348278/" title="Two of a kind by heipei, on Flickr"><img src="http://farm3.static.flickr.com/2110/2965348278_18fb0a9cdf.jpg" width="500" height="334" alt="Two of a kind" class="aligncenter"/></a><br />
In a shameless attempt to attract traffic I&#8217;m gonna do a short review of my new Macbook ;). I had been playing with the thought of buying a new laptop for a while now, and was almost certain it would be the Dell XPS 1330, since Apple didn&#8217;t really offer anything for me at that time (the Macbook Pros were too big and expensive, the Macbook Air was even more expensive and the Macbooks were made of plastic, which I really didn&#8217;t like). Right on time Apple released their new model, which is what I&#8217;m typing on right now ;)<span id="more-331"></span><br />
I&#8217;m really not a good reviewer since I don&#8217;t pay attention to some stuff most people think of as important. Also I was out of the loop for quite a while, so this new laptop brought not only a ridiculous leap in speed but also the new version of Mac OS (and an Intel x86 to run a lot of stuff not available on PPC).<br />
<b>Performance</b><br />
See, this is nice, I can say &#8220;compared to my G4 1.33Ghz I had been using before&#8230;&#8221;. Let&#8217;s just say that now I can view youtube-videos without 100% CPU usage, I can run two OSs in parallel, where the previous machine hardly ran one, I can compile for hours without the laptop breaking a sweat. The only thing you could count as a benchmark was that I fired up Urbanterror for about 10 seconds and it ran flawless on the native 1280&#215;800 resolution.<br />
Having a really really fast hard-drive is noticeable as well, deleting files doesn&#8217;t take forever and I&#8217;m able to really max out the 100mbit link. The DVD-drive looks good, the sound when waking up the laptop from sleep is much more quiet, as is the whole drive when watching a DVD.<br />
<a href="http://www.flickr.com/photos/heipei/2964508303/" title="Two of a kind by heipei, on Flickr"><img src="http://farm4.static.flickr.com/3197/2964508303_16bb789dd6.jpg" width="500" height="334" alt="Two of a kind" class="aligncenter"/></a><br />
<b>Looks and feel</b><br />
<a href="http://www.flickr.com/photos/heipei/2965349500/" title="Two of a kind by heipei, on Flickr"><img src="http://farm4.static.flickr.com/3241/2965349500_ab0e1ca87e_m.jpg" width="240" height="160" alt="Two of a kind" class="alignleft"/></a>Although I would have preferred another 12&#8243; model from Apple, this kind of 13&#8243; is still ok. The footprint is not that much bigger than my old Powerbook, and the Macbook is thinner (&lt;1cm thinner), and about 200g lighter than the Powerbook.<br />
The nice thing is that when closed, the new Macbook looks exactly like the bigger brother of the Powerbook. A few details have been improved. The screen closes like a magnet, snapping into place (like the previous Macbook), the sleep light is small and coupled to the ambient light sensor (good for sleeping next to it), and the edges are rounded below and above the Macbook, making it easy to grab it from a desk.<br />
The Unibody looks nice and feels strong enough (I usually carry my laptop with one hand grabbing the spot right of the trackpad when it is open). The edges may feel a little sharp, but that depends on how fat your arms are and if you type a lot ;).<br />
The Trackpad is just huge, bigger than my old trackpad and it&#8217;s mouse-button combined. The fact that it&#8217;s missing the actual button is absolutely no problem, you can click the whole pad or adopt the habit of just tapping the trackpad (two-finger-tap is a right-click, awesome).<a href="http://www.flickr.com/photos/heipei/2964509829/" title="Two of a kind by heipei, on Flickr"><img src="http://farm4.static.flickr.com/3187/2964509829_30cb15d5b4_m.jpg" width="240" height="160" alt="Two of a kind" class="alignright"/></a><br />
At first I disliked the look of the keyboard, with its black color and the gaps between the keys, but after a few hours I didn&#8217;t notice any difference, and the touch and sound of the keyboard is nice and quiet (expect the f-ing spacebar).<br />
The screen, yeah, you heard a lot about that. Let me tell you I was one the people who always began to curse when encountering one these glossy things in real-life. But there&#8217;s always some trade-off. And it does look nice. And so far I never had problems reading the screen, and I never got distracted by my own tired face staring back at me. The display is so ridiculously bright that I work below the maximum most of the time. The ambient light-sensor can adjust the display, which is another nice little feature and saves some minutes of battery in a dark environment.<br />
<b>Operating system and integration</b><br />
One of the reasons I bought Apple again (after really hating it for a while in between) was that I realized that many of the small things you take for granted would be missing or way more complicated on other systems with less thought-through approaches of combining hardware and software. My holiday in the US showed that in certain situations you just want a laptop which is available when you open it, which starts everything necessary when you connect your camera and you just have to click download and which makes it really easy to pick a wlan when you&#8217;re leaning against a wall in some hotel trying to find a spot with reception. At the same time I still have a shell and all my little text-ui programs.<br />
But enough of explaining my reasons. Mac OS 10.5 (Leopard) is a nice improvement over the previous version. Most of the stuff still works the same, the Terminal has been improved a little bit (with tabs for example, but still lacking 256 colors). The Finder still sucks donkey balls, and that is one department of the company Steve should have lined up and shot (when viewing your homedir the folders like &#8220;Music&#8221; and &#8220;Pictures&#8221; are now of the same color instead of the little colored images they used before). Good thing I don&#8217;t need it anyway. Instead of &#8220;Slideshow&#8221; there is Quickview, which seems to be the better choice for viewing large quantities of pictures and doesn&#8217;t discard your sort order. The Preview was improved in a few spots as well, as was Safari, though it&#8217;s still missing del.icio.us integration and a native way to do keyword-searches. Spaces is a native way to do virtual desktop, but I&#8217;m not using it so far.<br />
Having a speedy machine now I decided to install Quicksilver, which takes the pain out of many things and makes up for missing functionality of other programs. I use it to launch apps and to browse my del.icio.us bookmarks for example.<br />
<a href="http://www.flickr.com/photos/heipei/2975303604/" title="Back to back by heipei, on Flickr"><img src="http://farm4.static.flickr.com/3021/2975303604_b68f11a162.jpg" width="500" height="334" alt="Back to back" class="aligncenter"/></a><br />
<b>Conclusion</b><br />
Sorry for the messy review above, but I warned you before. The conclusion is that the Macbook is worth it&#8217;s price (I bought the 2Ghz, 2GB, 160GB version by the way), especially if your laptop is a little bit older. Whether you can live with the glossy screen is up to you, the best thing is to try one out for an afternoon, but it certainly isn&#8217;t a deal-breaker as many people suggested. I&#8217;m not missing anything about this laptop, not a FireWire-port, or a PC-Card slot or any other port. From a design-point of view it&#8217;s probably the most beautiful laptop I&#8217;ve seen so far, even more so when it&#8217;s closed. Here is a tip how to avoid being disappointed by the new hardware you just bought: Use your old stuff for about 4 years.</p>
]]></content:encoded>
			<wfw:commentRss>http://heipei.net/2008/10/26/macbook-review/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

