Joined February 2013
·

Larry Williamson

Creative and Technology Generalist
·
New York, New York
·
·
·

@bio_chemist -- I don't know that you need to use /../ in the case of mounting outside of Volumes, but /../ should work.

also, sometimes forcing version 3 NFS connectivity helps, by using vers=3

It is a matter of opinion and project really. I'm not saying to write code like this for everything. It's a tip not a rule.

@gaz_stephens i know. i could hardly believe it myself! after weeks of custom scripts and solutions (with their own issues, of course) ... reverting to simple path obfuscation is what finally did it. and it's just a three character difference!

@goudkamp are you sure you are using "/../Volumes/Public" in your auto_nfs? This is what the whole work-around is about. If you just use "/Volumes/Public", you have to manually create the mount point and it won't work automatically.

** OSX Mavericks deletes any user created folders in /Volumes on restart. **

similarly, do: $(document).on('click','.fancybutton', function(ev) { /* ... */ });

@depl0y: yeah. i was actually using launchctl and shell scripts right before i figured this out.

@rohitsinghal4u are you using web fonts or system fonts? you have to make sure the font is installed and available, or use a webfont (my suggestion)

I'm not really sure what you are talking about with the "20px" part :P

Are you using a pre-built version? Might consider building from source and making sure that all the requirements are met.

My OSX required an:
export LC_ALL=C

My OSX required an:
export LC_ALL=C

Achievements
1,216 Karma
164,619 Total ProTip Views
Interests & Skills