The Comment Selection command in the Source bundle has a bug. (Tested on the latest repo version.) If you select some markup that has an empty line, then hit Cmd-/, the empty line will screw up the comment markers. For example:
BEFORE
</SpeakingEvent> <SpeakingEvent>
AFTER
<!-- </SpeakingEvent> --> <!-- --><!-- <SpeakingEvent> -->
If you then try to uncomment by hitting Cmd-/ again, the block's entropy grows:
<!-- <!-- </SpeakingEvent> --> --> <!-- <!-- --> <!-- --><!-- <SpeakingEvent> --> -->
Interestingly, the above problem seems to occur only if the selected text contains a closing tag (as above).
I tried playing around with the comment.block.xml setting in the XML bundle but didn't get anywhere. Anybody know how this could be fixed?
Trevor
On 26/6/2006, at 9:34, Trevor Harmon wrote:
The Comment Selection command in the Source bundle has a bug. (Tested on the latest repo version.) If you select some markup that has an empty line, then hit Cmd-/, the empty line will screw up the comment markers. For example: [...] [...] I tried playing around with the comment.block.xml setting in the XML bundle but didn't get anywhere. Anybody know how this could be fixed?
I committed a fix to the Toggle Comment function.
-
Allan Odgaard -
Trevor Harmon