About 2 years ago I posted a question regarding whitespace inside comments causing files to be shown as different. This is still tripping me up in my workflow. Every single day.
The issue: when there is leading or trailing whitespace inside comment blocks (or // to end-of-line), BC treats that as a difference (if comments are set to be important, which I do want them to be).
So, for example
File1:
// this is a test
and
File2:
//this is a test<space>
will flag the file as different, despite leading/trailing whitespace being unchecked.
The same thing happens with multi-line comment blocks
File1:
/* this is
a test */
File2:
/* this is
<space>a test */
The reason this is happening is that the Comment grammar is taking precedence over the Default text settings, so the leading/trailing is considered part of the character "stream" from beginning to end.
This is really annoying and cumbersome when trying to sync code from other developers who fail to strip out these characters.
Basically, I want comments to be important, but leading/trailing whitespace on individual lines should not be.
Can we treat leading/trailing space characters separate from grammar definitions?
The issue: when there is leading or trailing whitespace inside comment blocks (or // to end-of-line), BC treats that as a difference (if comments are set to be important, which I do want them to be).
So, for example
File1:
// this is a test
and
File2:
//this is a test<space>
will flag the file as different, despite leading/trailing whitespace being unchecked.
The same thing happens with multi-line comment blocks
File1:
/* this is
a test */
File2:
/* this is
<space>a test */
The reason this is happening is that the Comment grammar is taking precedence over the Default text settings, so the leading/trailing is considered part of the character "stream" from beginning to end.
This is really annoying and cumbersome when trying to sync code from other developers who fail to strip out these characters.
Basically, I want comments to be important, but leading/trailing whitespace on individual lines should not be.
Can we treat leading/trailing space characters separate from grammar definitions?
Comment