StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Dug a little further, and I found that Xcode 3.x hides its syntax highlighting rules in <a href="http://enefekt.com/sansbrowser/2007/11/29/flex-support-for-xcode-3/" rel="nofollow noreferrer">xclangspec files</a>, so editing the appropriate file will allow you to change the rules to an extent.</p> <p>Files are stored here: </p> <pre><code>/Developer/Library/PrivateFrameworks/XcodeEdit.framework/Versions/A/Resources </code></pre> <p>In that directory, I opened BaseSupport.xclangspec and found the line that identified the URL protocol:</p> <pre><code> Syntax = { StartChars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ"; Chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789;/:@&=+$,-_.!~*'()%#"; Match = "^(acap|afp|afs|cid|data|fax|feed|file|ftp|go|gopher|http|https|imap|ldap|mailserver|mid|modem|news|nntp|opaquelocktoken|pop|prospero|rdar|rtsp|service|sip|soap\\.beep|soap\\.beeps|tel|telnet|tip|tn3270|urn|vemmi|wais|z39\\.50r|z39\\.50s)://([a-zA-Z0-9\\-_.]+/)?[a-zA-Z0-9;/?:@\\&=+$,\\-_.!~*'()%#]+$", "^(mailto|im):[a-zA-Z0-9\\-_]+@[a-zA-Z0-9\\-_\\.!%]+$", "^radar:[a-zA-Z0-9;/?:@\\&=+$,\\-_.!~*'()%#]+$", ); */ Type = "xcode.syntax.url"; }; </code></pre> <p>and changed the line for Match = to read:</p> <pre><code>Match = (); </code></pre> <p>This eliminated URL matching, but not mailto matching (which is in a separate rule below the first). I'm leaving that as an exercise for the reader ;-)</p> <p>Obviously, I could have been more selective, and I suspect that changing the Type line would be sufficient as well. Also, future versions of Xcode will likely overwrite this change, so I'll have to investigate putting the change into my own copy of BaseSupport.xclangspec and see if sticking it in ~/Library/Application Support works.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload