-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reformatting About_* for 80 columns - part 5 #1910
Conversation
@zjalexander - please review and merge |
*>&1 Sends all output types Test-Output *>> Test-Output.txt | ||
(*) to the success Test-Output *>&1 | ||
output stream. | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be rendered as a table instead of a code block?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried reformatting this in a table and this was cleaner than the Pandoc output of the table.
Format: {n,m} | ||
Logic: Specifies at least n, but no more than m, matches. | ||
Example: "abc" -match "\w{2,3}" | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
again, this is a codeblock instead of a table?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was a table and it was totally broken. It will not render properly with Pandoc for the .txt output. when we can use real markdown for these we can reformat it.
is different from the escape character for Windows PowerShell. The | ||
escape character for Windows PowerShell is the backtick character (`) (ASCII 96). | ||
Notice that the escape character for regular expressions, a backslash (\\), is | ||
different from the escape character for Windows PowerShell. The escape |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Windows PowerShell"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missed that one. Fixed now.
LastWriteTime Property System.DateTime LastWriteTime {get;set;} | ||
LastWriteTimeUtc Property System.DateTime LastWriteTimeUtc {get;set;} | ||
Length Property System.Int64 Length {get;} | ||
```Output |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
afaik "output" is not a valid codeblock language? it's not a problem but I'm just wondering if Docs is different than github in this respect
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is not but it ends up showing up as the "language" label on the rendered web page. This makes it clearer that they content is output.
the same computer or a different computer. The session state | ||
is maintained and commands in the PSSession continue to | ||
run while the session is disconnected. | ||
Beginning in Windows PowerShell 3.0, you can disconnect from a PSSession and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think "Windows" is intentional here because you do actually need windows for this to work, especially in 3.0. right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know the answer to that for sure. But since this is a "remoting" article, I left that as is. This will need to be reviewed and updated for the v6 release.
|
||
```powershell | ||
PS C:\> Receive-PSSession -ComputerName Server02 -Name Session3 -OutTarget Job | ||
PS C:\> Receive-PSSession -ComputerName Server02 -Name Session3 ` | ||
-OutTarget Job | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think you want to terminate the powershell codeblock and create a new codeblock for the output, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ultimately yes, I was going for expedience to get these files reformatted and republished. We also need to close on the "PS prompt" issue. Once that is decided we can focus on fixing the output issue as well.
reformatting About_* for 80 columns - part 5
Reformatted files to fit in 80 columns per Issue #1806. No other changes to the content except where noted.
Version(s) of document impacted