<p dir="auto">Many comments in the .less-Files start with <code class="notranslate">//**</code> which in a lot of programming languages is equal to a multi-column comment (<code class="notranslate">/* ... */</code>). Therefore any IDE not perfectly adjusted to LESS syntax highlighting (such as VisualStudio) tend to interpret these comments as multi-column, which is in the case of the bootstrap sources basically <em>every</em> following line, making the code more or less unreadable.</p>
<p dir="auto">Sure, an answer to this request could be "go and set up a proper highlighting" <g-emoji class="g-emoji" alias="wink" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f609.png">😉</g-emoji> But in the end this would be a <em>very minor change without drawbacks</em> (afaik) but nevertheless improving usability of the bootstrap sources.</p>
<p dir="auto">An example of what I mean is in <em>variables.less</em>, line 27:<br>
<code class="notranslate">//** Background color for </code><code class="notranslate">.</code><br>
which without any effort could be changed to<br>
<code class="notranslate">// ** Background color for </code><code class="notranslate">.</code> (note the added space in col 3)</p>
<p dir="auto">I'm not sure why the comments in the <code class="notranslate">variables.less</code> got changed to this style <code class="notranslate">//**</code>, but it my opinion it was a brave move.</p>
<p dir="auto">For me at least it prevents compilation when using the nodejs compiler <code class="notranslate">lessc</code>.</p>
<p dir="auto">At also breaks the syntax highlighting in my IDE, Visual Studio 2013</p>