Go to Views->Content Templates and either create or edit a template. View the main template edit box with syntax highlighting off. Everything looks okay. Now turn syntax highlighting on, and the first three characters on the left of each line are blocked from view by the codemirror line number div.
I also have a second observation re: templates. I like keeping my sites organized, so when you guys came out with Layouts, I immediately started to use it to organizing my sites, typically by using a parent layout that contains the header and footer (the stuff that stays the same), and then using child layouts to define the stuff that changes (content and sidebar). I then assign my layouts to pages, etc., and everything works great.
However, I then began using content templates for single pages, and here is what I found:
1. If my child layout calls for Post Content in the content area, and I insert my content template shortcode in the page's content editor (e.g. [wpv-post-body view_template="account"]), everything works as expected.
2. If I remove the content template shortcode from the page's content area, and instead select the content template in the select box in the right sidebar, nothing displays.
3. If I clear the select box in the right sidebar, such that the page now only has a layout assigned to it, and I then go back to the layout, and in the Post Content cell, I select "Display the cell content using post fields" and choose the appropriate content template, everything displays properly again.
Obviously, point 2 needs to be fixed. If we apply a content template to post content, it should work regardless of the method we use. But my broader complaint here is that this seems like a convoluted model. If I use the approach described in point 3 above, and I then return to the page and insert a different content template shortcode into the main post edit box, this action no longer has any effect, i.e. the approach in point 3 appears to supersede the presence of a shortcode inserted directly into the post content. So now I have a situation where the shortcode may or may not work, depending one what I've set elsewhere, i.e. out of my immediate view and perhaps out of mind. On a large site, this kind of thing could cause a lot of headaches. If you insist on retaining the flexibility to use content templates in three different ways, then I think you have to help govern its use (i.e. disable buttons, give warnings, etc.). Otherwise, you'll only sow confusion.