-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix keyword table #17855
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 keyword table #17855
Conversation
It's a little unfortunate to resort to raw HTML, could this be used instead?
That renders as a table in rustdoc locally for me |
You could probably delete some of the blank rows as well |
See the above screenshot, it makes the output look gross :( EDIT: by 'above' i mean 'in the original ticket' |
If you don't have the same number of tds, it recenters them per line, which makes the output look ugly. |
Markdown tables require a header, and we don't want one. Fixes rust-lang#17528
df16642
to
3610f8f
Compare
Time to advocate asciidoc:
produces the expected output. |
I pushed a commit with the alternative fix we talked about in IRC https://botbot.me/mozilla/rust-internals/2014-10-07/?msg=23049256&page=7 |
@@ -187,6 +187,8 @@ grammar as double-quoted strings. Other tokens have exact rules given. | |||
|
|||
The keywords are the following strings, organized by first letter: | |||
|
|||
<div id="keywords"> |
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.
Is the contents actually rendered as a table? I was under the impression that markdown was not processed inside HTML tags.
…richton Markdown tables require a header, and we don't want one. Fixes #17528
Markdown tables require a header, and we don't want one.
Fixes #17528