I just upgraded to Xcode 4 (from 3.2.4) and while there are a lot of behavior/preference changes I need to get used to, I'd like to get a couple issues handled sooner rather than later.
Can I exclude the delimiters when balancing delimiters? In v3.x, you could balance delimiters and the selection would exclude the enclosing braces. Is that possible with v4?
Is there an equivalent to the advanced find/search available in v3? Used to ctrl-click on a symbol and select search in project which opened a new search window. You could also define different search sets to use when searching. I can't find any similar behavior in v4.
Finally, does anyone know if the Apple developer forums are available to users who have only registered as a developer (but not joined)?
Thanks!
Under the Help menu in Xcode 4 there is an option for Xcode User Guide which covers what you can do with Xcode 4. I have been through it and it seems pretty light so far so it may not have what you need, but it is a good place to start.
I also did a search in Help and quickly found that you can change this setting with a checkbox in Preferences under Text Editing. I've included a screenshot with the option highlighted below.
Related
Recently switched editor and I would like to know if it is possible in Coda 2 to have indent guides like notepad++, Like this image i found: http://www.freesoftwareworkshop.com/wp-content/uploads/2008/11/notepad-plusplus.png
I am talking about the gray dotted vertical line when tabbing. I hope this is possible in Coda or some plugin i could install for it.
I have tried searching Google but its a hard example to search for and did not find any result.
I'm currently using Coda's 2.5b8 beta and can confirm that this feature is now a part of Coda and should be included in their next release.
In the Preferences>Editor settings, there is a checkbox labeled "Show indentation guides". This is the setting you'll want checked.
As of 03/19/2014, this is only available to those with beta access.
I too want this feature desperately and have searched high and low to find it but with no success.
I have however put in a request with them to include this in there next major release so I'm keeping my fingers crossed.
I'm trying to find a way to disable Sublime Text 3's minimap for a single syntax (Markdown) only and I'm not having much luck.
I've found a lot of references to adding "show_minimap": false, to your preferences both here and elsewhere but it doesn't seem to do anything regardless of whether I put it in Markdown.sublime-settings or Preferences.sublime-settings (I am restarting Sublime Text after changing the setting just to be safe).
The View/Hide Minimap menu item works globally but I can't set it for a specific syntax.
In most of the threads I've found I see some people saying that the setting doesn't work for them with other people saying it does but none of them seem to have an answer why and how you might fix it.
Has the syntax for that setting changed or has it simply been removed? I don't see it mentioned in the unofficial documentation.
If it does (still) exist is it something you can apply to a specific syntax or does it have to be a global setting?
Thanks!
I've tried both "hide_minimap": true and "show_minimap": false (alone and in combination) with ST2 2.0.2 and ST3 Build 3056 on XP, and nothing seems to work. I don't know the versions/platforms the answerers/commenters on your linked questions were using, but it seems that either the behavior was somehow removed recently, or it's platform-specific (maybe a little of both). I went back through the changelogs for ST2, ST3 Public Beta, and the ST3 dev builds and found a number of references to the minimap, but nothing to indicate that the functionality you're looking for had been removed intentionally.
We don't know if it makes a difference to the developer, but the community maintains an issue tracker on GitHub for things like this. Feel free to submit a new issue, with as much information as possible about what you've tried and the platform(s) and version(s) used, and we'll see where it goes.
If you're the plugin-writing type, there theoretically is a way around this, though. You could write an event listener that checks the scope of any newly-opened files, and if it matches text.html.markdown (or whichever type(s) of file for which you'd like to have the minimap hidden), it could execute the toggle_minimap command, which is what is fired when you select View -> Hide Minimap.
I'm working on that plugin, but it's not coming along very quickly. I'll report back if I can get it to work.
In OS X, Sublime text 3 try:
CMD+`
In Windows perhaps:
CTRL+`
I have Xcode 4.2. At some point the rich text just stopped working. The only elements that it is selecting are strings, comments and number values. The rest is just written in white (I'm using the Midnight option).
I've tried restarting my machine, Xcode and changing my preferences (to Low Key and then back to Midnight). This only is happening on one project and not the others. Any ideas on how to correct this? It is surprising how this makes coding a bit more strenuous on the eyes.
Found it!
Go to Organizer --> Projects --> YourRichTextFailingProject --> then hit the button Delete under Derived Data.
Something that I have always wanted in TextMate was a different way to open files.
For instance, when I open a file in TextMate, I would love the active tab to default in position 1. Then when I open another tab, that tab should take over position 1, and the rest will shuffle down the list.
Are there any plugins for TextMate that provide this type of functionality?
I don't believe such a plugin exists.
There are two plugins providing supercharged alternatives to the project drawer:
MissingDrawer
ProjectPlus
They don't provide the feature you want but you could try to get in touch with their authors to see if they can add it or point you in the right direction.
The ProjectPlus project has been pretty much dead for years (there are unanswered pull requests from january/february 2011) but there seems to be some action on MissingDrawer.
If you know Objective C you may be able to hack something from their sources.
Whatever the outcome it may work for the "click on a file in the drawer" way of opening a file but not for other ways.
Did you look at TextMate's .plist? I've heard there are some hidden gems there.
Xcode search just isn't working the way I expect it to. What am I doing wrong?
"Project Find" (cmd-shift-F) often turns up zero results when I KNOW that there are valid hits. For example, searching for "Search Results" (no quotes) ironically returns 0 hits, even though I have a .m project file open with the string #"Search Results" sitting right in front of me. My Find Options are set as loosely as i can make then, case-insensitive, Search In Open Projects, All Candidate Files, All Files in this Project, etc.
The Search bar in the upper right of my main project window doesn't seem to behave like Project Find, nor does it seem to search the currently open document. What does it do?
Searching for "UIView" in the Help menu search turns up zero hits, even though if I open up the Developer Documentation from the Help menu and search from that window it returns plenty of hits.
Help menu searches only for menu entries (try searching for "Paste") and end-user documentation (how to use the software itself, not how to develop it).
Use documentation viewer to search within developer documentation (it lets you switch between fulltext and API names search, select OS version and language).
Check what options you've set in project search – it might be set to match whole identifiers only, be case-sensitive, search only selected files, etc.
Select:
In Project
Textual
Contains
Ignore case
Uncheck:
Display Resutlts in Find Smart Group
This might help :
If you are searching files in project then select "Ignoring case". Below is screenshot for the same.
If you are searching a particular file then select magnifier -> Edit finding option.. -> Select/Unselect Matching case accordingly. Below is screenshot for the same.
In my case the Pods project had an issue and Xcode could open it. Thus, although the files were there, Xcode could search through them.