Yes, you may put comments in there. They however must start at the beginning of a line. cf. http://git-scm.com/book/en/Git-Basics-Recording-Changes-to-the-Repository#Ignoring-Files The rules for the patterns you can put in the .gitignore file are as follows: – Blank lines or lines starting with # are ignored. […] The comment character is #, example: # no .a files … Read more
#!/usr/bin/env ruby =begin Every body mentioned this way to have multiline comments. The =begin and =end must be at the beginning of the line or it will be a syntax error. =end puts “Hello world!” <<-DOC Also, you could create a docstring. which… DOC puts “Hello world!” “..is kinda ugly and creates a String instance, … Read more
You can use that style of comment across multiple lines (which exists also in HTML) <detail> <band height=”20″> <!– Hello, I am a multi-line XML comment <staticText> <reportElement x=”180″ y=”0″ width=”200″ height=”20″/> <text><![CDATA[Hello World!]]></text> </staticText> –> </band> </detail>
In PowerShell V1 there’s only # to make the text after it a comment. # This is a comment in PowerShell In PowerShell V2 <# #> can be used for block comments and more specifically for help comments. #REQUIRES -Version 2.0 <# .SYNOPSIS A brief description of the function or script. This keyword can be … Read more
Use :: or REM :: commenttttttttttt REM commenttttttttttt BUT (as people noted): if they are not in the beginning of line, then add & character: your commands here & :: commenttttttttttt Inside nested parts (IF/ELSE, FOR loops, etc…) :: should be followed with normal line, otherwise it gives error (use REM there). :: may also … Read more
You can use triple-quoted strings. When they’re not a docstring (the first thing in a class/function/module), they are ignored. ”’ This is a multiline comment. ”’ (Make sure to indent the leading ”’ appropriately to avoid an IndentationError.) Guido van Rossum (creator of Python) tweeted this as a “pro tip”. However, Python’s style guide, PEP8, … Read more
Unicode decoding takes place before any other lexical translation. The key benefit of this is that it makes it trivial to go back and forth between ASCII and any other encoding. You don’t even need to figure out where comments begin and end! As stated in JLS Section 3.3 this allows any ASCII based tool … Read more
For those tasks I use most of the time block selection. Put your cursor on the first # character, press CtrlV (or CtrlQ for gVim), and go down until the last commented line and press x, that will delete all the # characters vertically. For commenting a block of text is almost the same: First, … Read more
YAML supports inline comments, but does not support block comments. From Wikipedia: Comments begin with the number sign ( # ), can start anywhere on a line, and continue until the end of the line A comparison with JSON, also from Wikipedia: The syntax differences are subtle and seldom arise in practice: JSON allows extended … Read more
I believe that all the previously proposed solutions (apart from those that require specific implementations) result in the comments being included in the output HTML, even if they are not displayed. If you want a comment that is strictly for yourself (readers of the converted document should not be able to see it, even with … Read more