Placing comment in export mte (for csv)

Tried searching most of the help pages, but only found reference to the comment tag. Is it possible to place a comment within the export mte to explain the code? Tnx

You can embed the code-line in <!-- -->

<!-- This is my explanation for the code -->

1 Like

To be clear(er), I want the comment to not appear in the generated output; the output should be unaffected by the comment.

Thanks for the reply. For me, this is written to the output.

If I insert the above comment line in one of the example export scripts like this:

			<td$if($odd(%_counter%), class="odd",)>$meta(artist)</td>
            <!-- This is my explanation for the code -->			
			<td$if($odd(%_counter%), class="odd",)>%title%</td>
            <td$if($odd(%_counter%), class="odd",)>%album%</td>

The comment will NOT appear in the export. If you show us your code, it will be easier for us to help.

Aha, I neglected to mention this is for csv output, not html. Makes all the difference in the world. A snippet:

$loop(%_filename_ext%)"$replace($regexp($regexp($regexp(%_filename_ext%,\r\n,; ),\r,; ),\n,; ),",)",$puts(a
,)"$replace($regexp($regexp($regexp(%_folderpath%,\r\n,; ),\r,; ),\n,; ),",)",

ohrenkino had suggested a mis-use of $puts into a dummy variable, but that solution had a blank line in the output.
Thanks for the help!

That is mainly a problem of how you format the code - unfortunately, the layout of the code is also the layout of the output. So if you put the comment into an extra line, then this still acts as extra line in the output. The only way around it would be to keep the misused $puts() in the same line as the code.

Thanks, that's helpful.
To store examples so it can be used by others:

$puts(for_comment,Misused puts() used to show a comment here)$loop(%_filename_ext%)"$replace($regexp(


$loop(%_filename_ext%)"$replace($regexp( ...,$puts(a
,)"$puts(for_comment,Misused puts() shows comment for following code)"$replace($regexp(%artist%,...)"

Code for comment must be in-line with rest of code. Thanks @ohrenkino