Skip to content

Conversation

BurdetteLamar
Copy link
Member

In working on a markdown reference, I've noticed that the markup reference could use some work, too.

This adds some clarity to the intro, and has a couple of other small tweaks.

Much more to come.

# a function that implements a Ruby method,
# or otherwise immediately precedes the definition of a Ruby object,
# becomes the documentation for that object.
# - <tt>.rdoc</tt> (\RDoc markup text file) or <tt>.md</tt> (\RDoc markdown text file):
Copy link
Member

Choose a reason for hiding this comment

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

It seems like we're losing the information here that we generate docs from markdown files.

Copy link
Member Author

Choose a reason for hiding this comment

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

My thinking is that this is the markup reference. I don't know whether a markup file can declare itself as markdown. But will restore if you like.

Copy link
Member

Choose a reason for hiding this comment

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

Ah I see. Might be good to include it in a separate bullet point and make it clear that the rest of this guide doesn't apply since it's markdown. This section seems to list all of the sources that RDoc generates documentation from.

Copy link
Member Author

Choose a reason for hiding this comment

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

Info added.

@peterzhu2118 peterzhu2118 merged commit f2fefe0 into ruby:master Aug 27, 2025
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants