For people that routinely help with Powershell or other code questions, there’s some neat tricks you can do with Code formatting. You can put 3 back ticks before and after your code ``` in order to have code show up more readable. You can also specify the specific language formatting such as ```bash. Supported languages as of this post: apache, bash, cs, cpp, css, coffeescript, diff, xml, http, ini, json, java, javascript, makefile, markdown, nginx, objectivec, ruby, perl, php, python, sql, handlebars. Sadly no powershell.
I doubt many people will use this next part, but I find it interesting and others may find it useful.
You can also use a code block with <code> and </code> which puts a little break between each line. In addition you can have some fun with highlighting.
$x=test Mark text as delete <del>$x=test</del>
$x=$test Mark text as inserted <ins>$x=test</ins>
$x=$x+1 Highlight the text <mark>$x=test</mark>
Example using ``` and code formatting
Suppose someone posts a not working example:
How can I get a list of users created dates? It doesn’t show the created date.
Foreach ($User in $Userlist) {
$Userinfo = Get-ADUser $User | Select samaccountname,created
}
You could reply this way, and mark up the code.
You need to explicitly add the property since it’s not a default property
Foreach ($User in $Userlist) {
$Userinfo = Get-ADUser $User -property created | Select samaccountname,created
}
Note that markdown doesn’t work in blocks where you use ``` on either side. You have to use the code markdown instead. To indent, throw a at the start (or more than one). You don’t need to use code to just highlight text.
If you’re wondering how I was able to put the mark down codes in the text without them firing, use < in place of the opening < (less than).
At some point perhaps we could collectively put together a good markdown document. There are examples all over for discourse, but it’s not really in a good unified doc that I’ve found.
