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

Fix macro references in Bikeshed documentation #2773

Closed
wants to merge 2 commits into from

Conversation

ferdnyc
Copy link

@ferdnyc ferdnyc commented Jan 25, 2024

Since 16c53d7 the syntax `[MACRO]` is no longer protected from replacement, and an escaped `\[MACRO]` reference will be output as <code>\[MACRO]</code>.
So, replace all `[MACRO]` references with <code>\[MACRO]</code> in the bikeshed documentation source, which is correctly translated into the output document as <code>[MACRO]</code>.

The regenerated docs/index.html (included) differs only by code changes made to bikeshed's HTML generation boilerplate since the last time it was generated.

Affects #2765 (specifically, the docs/index.html generated there)

Since 16c53d7 the syntax '`[MACRO]`' is no longer protected from
replacement, and an escaped '`\[MACRO]`' reference will be output as
'`<code>\[MACRO]</code>`'.
So, replace all '`[MACRO]`' references with '`<code>\[MACRO]</code>`'
in the bikeshed source, which is correctly translated into the output
document as '`<code>[MACRO]</code>`'.
@ferdnyc
Copy link
Author

ferdnyc commented Jan 25, 2024

Ironically, the only reference that doesn't have to be adjusted is this one:

like `\[TITLE]`.

As the new behavior is the same as the old behavior in that particular instance.

@tabatkins
Copy link
Collaborator

This problem doesn't reproduce in the current version of Bikeshed. I have to assume the issue is the docs being generated with an old version.

@tabatkins tabatkins closed this Jan 25, 2024
@ferdnyc ferdnyc deleted the fix-docs-bs branch January 25, 2024 21:19
@ferdnyc
Copy link
Author

ferdnyc commented Jan 25, 2024

@tabatkins

This problem doesn't reproduce in the current version of Bikeshed. I have to assume the issue is the docs being generated with an old version.

Agreed, though I don't know how as I was working in a venv with a pip install -e . version of bikeshed.

*shrug* Oh, well. Apologies for the noise.

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.

2 participants