Skip to content
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

Escaping '\' character in Markdown #2581

Closed
wants to merge 3 commits into from
Closed

Escaping '\' character in Markdown #2581

wants to merge 3 commits into from

Conversation

nmontesinoc
Copy link
Contributor

Details:
Since the command "(Get-ChildItem -Path "$Env:SystemRoot\prefetch*.pf" | Measure-Object).Count" is not in a codebox, the '*' character is being escaped by Markdown.

It can be whether added to a codebox or escaped in the Markdown text. I've done the later.

Copy link
Collaborator

@clr2of8 clr2of8 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your first time contribution and helping keep things in order over here. I like the change that you propose but since all of the markdown (md) files are automatically generated from their YAML counterparts, this change will be immediately overwritten. Could you instead make the correction to the YAML as shown here and as soon as the new PR is merged, the markdown will be automatically updated. Also, I suggest putt the command in backtick marks (`) to get a code block in markdown instead of using escaping because there are other places that the description in yaml are presented to the user outside of the markdown (e.g. on the powershell command line) and it need to read well in both cases. Thx!

@clr2of8 clr2of8 self-assigned this Nov 2, 2023
@clr2of8
Copy link
Collaborator

clr2of8 commented Nov 8, 2023

closing this one for now. feel free to resubmit as suggested

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants