Tag Info

New answers tagged

0

I use Testflight OS X desktop app to upload a binary and it usually takes minutes for recipients to receive build notification emails.


0

The Xcode template for C++ files does have #include <stdio.h>. To change this you have to create a template of your own - See several Stack Overflow questions here or here


0

Here's what worked for me: Good network connection Enough free space (if you need a few GiB, just sudo rm -f /var/vm/sleepimage, osx will recreate it as needed) Check 3rd-party app firewall for interfering "deny" rules Close App Store rm -rf /private/var/folders/pd/*/C/com.apple.appstore Reboot Run updates (works!) To see what's going on while updates ...


1

You can use BetterTouchTool to rebind TAB ⇥ key to ⌘ CMD+] only for Xcode.app. BetterTouchTool can be downloaded here. This is how this should look like: I've tested this and it works for me.


0

There may be better answers coming but if not. I would either Partition the Hard drive and create a second bootable partition then use the older Xcode there. Or Install it on a different Machine. I support some apps on 10.6 and ran into similar problems and now use the older Xcode on another Machine. But have used Partitioning in the past for even older ...


0

It is assumed the making alias or linking to different gcc binaries will make them use their own include before the default system include folder.


0

Side note: if you use DefaultFolderX (which has lots of other handy features), you can set an 'advanced option' so that all you need to hold is the Option key when selection Open or Save to be able to access all files/folders.


1

Pressing ⌘⇧G (Cmd+Shift+G) in any Finder window or standard file open/save dialog will bring up a little prompt: You can enter any path you want into this prompt. Using ⌘⇧G to get to this prompt will show the last path you entered, which is very handy for saving multiple files to the same hidden destination. In Open or Save dialogs you can also get ...


9

The built in way to do this by using a key combination when in the save/open dialogs to toggle the hidden files to visible or hidden Update: This shortcut works in all views, But in column view it does not update the view to show the change until you navigate to another directory. Not sure why this is the behaviour. But you can toggle it in column view ...


3

Referring to the screenshot in your original question: Just drag the folder (_EXTERNAL_DATA...) from your Finder window on the right into the save dialog on the left. The save dialog will now be sitting at the folder you dragged into it. If you have already opened the folder in your Finder window, just drag the little folder icon from the Finder window's ...


1

What if you add said hidden folder to the Finder sidebar? It will then show up in an open/save panel. For example, I mess around in ~/Library from time to time, enough that I added it to the sidebar. Now, when I go to and open or save panel, I'm able to jump right to it.


7

Which version of OS X are you using? When I tested this on Yosemite, if I entered ~ or / it brought up this: in which you can enter the path to the directory of your choice. Also if you just put in the directory such as ~/Library Then it will take the file selector to that directory and allow you to drill down.


0

I had encountered this frustrating situation as well. Reinstalling Xcode 6.1 and then running 'xcode-select' solved the problem.


2

You need to run xcode-select --switch [path] as descriped here: http://stackoverflow.com/questions/9600615/xcode-stops-working-after-set-xcode-select-switch And here is Apples documentation: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/xcode-select.1.html


0

I now crtl click on the Project container or a file inside to get to the Project folder or file.


0

Run free utility Onyx (http://www.titanium.free.fr/onyx.html), tab Automation, check all operations. This shall fix extra icons (and many other inconsistencies too) after reboot :)


0

This issue may be related to the preference configuration file. Delete the stack and re-recreate it, it should work.


0

I had the same issue in Yosemite. Tried with the files mentioned here, but it was still crashing. Giving admin rights to my OS X user seemed to "solve" the issue. In other words, running the app as a "Standard" user and seemed to cause the crash for me. Still it is not a nice solution, but maybe it helps some people or give insight for a better solution ...



Top 50 recent answers are included