By default Yosemite doesn’t like users to auto-login when the system starts. Instead you have to select a user, type in the password, and then the system starts to boot. Not necessarily what we want.
To disable this feature you usually head over to
Users and Groups
and pick your default user from that handy drop down menu. Notice however that this is greyed out on Yosemite:
So what gives?
Turns out that this option is not available if you’ve agreed to encrypt your disk via FileVault. And it makes sense too: otherwise your hard disk data could be accessed upon boot without a password, rendering this feature useless.
Hence, to bring back automatic logins, turn off FileVault under
Security and Privacy
According to this system, I can do that in about 32 days…
Notice that if you use your iCloud password as the login password, auto-logins are also disabled. In which case, change your login password to a “separate password”, switch off FileVault and voila – auto logins are back at your disposal.
Every time I try to update Microsoft Office 2011 on my Mac I get this ridiculous window popping up. No matter how hard you try, those two services – Microsoft Database Daemon and SyncServicesAgent – keep relaunching themselves, forever preventing you to apply the update.
Clearly Microsoft (or Apple) don’t want us to update Office for Mac:
Usually I give up and live without such updates. I only use M$ Office once in a blue moon and really don’t care. Today I got curious and researched this phenomenon – and thought I’d tell you about it.
Several suggestions are available to combat this superb example of a terrible user experience:
rename those processes
log out, then log back in with the shift key held down
go offline just before this message comes up
kill the processes with the Activity Monitor Utility
None of those suggestions worked for me, and besides: what a hack any of these solutions are to apply a simple security patch.
What did work was a very clever suggestion by someone named vrleboss: Use a while loop on the command line and continually kill those processes until you’re done.
Here’s how to do it: Open the Terminal utility on your Mac and paste the following code:
You can do this without quitting anything else, even while the pesky “close applications” window is displayed. Make sure the whole command is on the same line. The is a BASH loop that will find both processes and kill them as soon as they start up again. Don’t worry about the continuous text output in the window.
Back in the Microsoft Updater window, hit “Close Applications and Install”. Now it works!
Once the update is applied, head back to the Terminal window and press CTRL+C – this will stop the killing loop. Close Terminal and Office for Mac is finally updated.
Then repeat this process next week, when another 140MB of updates will have to be applied.
In this screencast I will show you how to bind a Table View to an Array Controller in Cocoa, using Xcode 5.1 and OS X Mavericks. We’re using Core Data to save our entries and – check it out – we’re not writing a single line of code!
Cocoa Bindings is one of the most exciting features in OS X development for me, and I hope that one day it’ll find its way into iOS too.
In this video I will show you how to use the Git Branch feature in Xcode 5.1.
Branches are helpful if you’re developing your app. You can isolate a “working” version, create a new branch and fiddle with new features that may destabilise your project. You can then commit your changes – working or not – to a separate branch, and when all is stable again you can merge them back into the master project.
I use this feature for plugin and theme development, in fact for any “group of files” that will change over time. If you’re not using Xcode, take a look at the GitHub Apps which are available for Mac and Windows. They make version control a breeze on your local system, integrate flawlessly with GitHub.com as well as SSH remotes on your own server.
In this video I will show you how to make use of Tags in Git. This is not supported in Xcode or GitHub for Mac at the time of this recording (April 2014). I will also show you how to utilise the Tag/Release feature on GitHub.com.
Tags are a useful feature if you want to mark versions of your software before you add new features. With Tags you can always go back to the code of a release.
We’re using Xcode 5.1 and the Terminal utility for this.
I use tags and branches for plugin and theme development too, in fact for any “group of files” that will change over time. If you’re not using Xcode, take a look at the GitHub Apps which are available for Mac and Windows. They make version control a breeze on your local system, integrate flawlessly with GitHub.com as well as SSH remotes on your own server.
Choose the full version without ZEND Server (not necessary as we’re using MAMP). Unpack the download and put it somewhere safe. I’m adding mine to my Documents directory. I’ll also rename my folder to something like “ZendFramework” without the version number.
To access it from anywhere on our machine we’ll create an alias named “zf”. zf is a shell script provided by the framework that we’ll need throughout our development journey with ZEND. Let’s to this in a Terminal session:
Replace the path with your own. Notice the call to /bin/zf.sh which is the “real” shell script. Our alias has just made this universal and accessible without having to mess with our shell path.