***EDIT 7/12/2013 I replaced the format file with a new version. See post #3 below
I couldn't find any BC format for SAS, so I created one and thought I'd share it here. Basically I copied keywords, operators, procedures and other info out of an Ultraedit Wordfile for SAS 9.1.3. For all intents and purposes this should work fine for whatever version of SAS you're using.
I should note that I added some custom grammar element names like "SAS Procedure" and a few others. And much other stuff just got bundled into keywords.
So what you want to do is go to Tools->Options... File Views->Display and from there you will find the newly named elements and can set the formatting however you'd like.
I attempted to export the settings too so the formatting for the custom elements could be automatically imported, but I really didn't want to send my whole settings file. One thing I tried to do was edit the XML file so it only contained the relevant tags for the File Views. So it looked something like:
But when I tested an import, what it did was erase (set to default) all of the other options that were left out of the xml -- which is obviously not what anyone wants to happen.
Maybe someone knows a way around that problem? Otherwise, not that important.
This is my first time working with BC file format rules so I sort of muddled my way through it. I just copied the regex for numbers from Perl or something. Close enough, I'm sure.
Anyway, I hope this helps some of the other BC users who use SAS. There's got to be at least 5-6 other people in that subset!
I couldn't find any BC format for SAS, so I created one and thought I'd share it here. Basically I copied keywords, operators, procedures and other info out of an Ultraedit Wordfile for SAS 9.1.3. For all intents and purposes this should work fine for whatever version of SAS you're using.
I should note that I added some custom grammar element names like "SAS Procedure" and a few others. And much other stuff just got bundled into keywords.
So what you want to do is go to Tools->Options... File Views->Display and from there you will find the newly named elements and can set the formatting however you'd like.
I attempted to export the settings too so the formatting for the custom elements could be automatically imported, but I really didn't want to send my whole settings file. One thing I tried to do was edit the XML file so it only contained the relevant tags for the File Views. So it looked something like:
Code:
<?xml version="1.0" encoding="UTF-8"?> <!-- Produced by Beyond Compare 3 from Scooter Software --> <BCPreferences> <TFilePrefs> <AlignedColor Value="$FFFF00"/> <BGColor Value="$FF000005"/> <CenterColor Value="$2585B8"/> <CheckForChanges Value="True"/> <CheckForChangesAutoReload Value="False"/> <CompareAsMerge Value="False"/> <ConflictHueShift Value="3"/> <CurBGColor Value="-"/> <CurFGColor Value="-"/> <CurOverUnderOnly Value="False"/> <DiffShift Value="0"/> <DimPct Value="20"/> <EditedColor Value="$6CE9FF"/> <EditorFontStr Value=""/> <ElementPSs> <Item> <ElementStr Value="SAS Procedure"/> <ValueStr Value="$FF0000"/> </Item> <!--and so on for the rest of TFilePrefs -->
Maybe someone knows a way around that problem? Otherwise, not that important.
This is my first time working with BC file format rules so I sort of muddled my way through it. I just copied the regex for numbers from Perl or something. Close enough, I'm sure.
Anyway, I hope this helps some of the other BC users who use SAS. There's got to be at least 5-6 other people in that subset!
Comment