• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Text macro specifications submenu
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Text macro specifications submenu


  • Subject: Re: Text macro specifications submenu
  • From: Rush Manbert <email@hidden>
  • Date: Tue, 18 Jul 2006 10:40:57 -0700

Steve Mills wrote:
On Jul 18, 2006, at 09:02, James Bucanek wrote:

Text macros are one of those user extensible, but largely undocumented, features of Xcode.

It's also one of the topics that didn't make it into my book due to space constraints. Which is good news for you: It's available as a free bonus section that you can download here <http://www.wrox.com/ WileyCDA/WroxTitle/productCd-047175479X.html>. Follow the link to the download code section, then get the bonus chapters disk image. The file is "ch 19 - Custom Text Macros."


Looks like the override mechanism really doesn't work in Xcode. I added my own .xctxtmacro file in ~/Library/Application Support/Apple/ Developer Tools/Specifications/ and copied the main C definition from Xcode's C.xctxtmacro, changing only the PreExpressionsSpacing string from " " to "". Your doc says that this should override Xcode's definition, but using any of the other macros result in the space still being there.

{
{
Identifier = c;
Name = "C";
IsMenu = YES;
DefaultSettings = {
PreExpressionsSpacing = ""; // space between keyword and opening paren
InExpressionsSpacing = ""; // space between paren and expression
CaseStatementSpacing = ""; // indentation of a case statement
BlockSeparator = " "; // space between closing paren and brace (can include a newline)
PostBlockSeparator = "\n"; // space after a brace and before a new block (can include a newline)
};
ComputerLanguages = ( c );
},
}


Any ideas?

Steve,

I can attest that it does work, and I used James' example to make mine. (I changed the formatting of the inserted code and added my own code insertion macros.)

I actually copied the entire Apple provided file over, then edited it. I can't tell from your description if you did that, or just tried to use the section of the file you show above. Maybe that's the difference? (What you show certainly looks correct as far as formatting is concerned.)

- Rush
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Text macro specifications submenu
      • From: Steve Mills <email@hidden>
References: 
 >Re: Text macro specifications submenu (From: James Bucanek <email@hidden>)
 >Re: Text macro specifications submenu (From: Steve Mills <email@hidden>)
 >Re: Text macro specifications submenu (From: Steve Mills <email@hidden>)

  • Prev by Date: Speed drop after QuickTime and iTunes updates
  • Next by Date: Re: Text macro specifications submenu
  • Previous by thread: Re: Text macro specifications submenu
  • Next by thread: Re: Text macro specifications submenu
  • Index(es):
    • Date
    • Thread