Skip to content

Move shebang into its own subchapter#2199

Open
traviscross wants to merge 1 commit intomasterfrom
TC/add-shebang-chapter
Open

Move shebang into its own subchapter#2199
traviscross wants to merge 1 commit intomasterfrom
TC/add-shebang-chapter

Conversation

@traviscross
Copy link
Contributor

In #2192, we extended our documentation about shebangs but kept it in Input Format under a section on shebang removal. But really, this section is mostly now about documenting what a shebang is, for our purposes.

Let's separate this out into a new subchapter.

We'll keep the rule about shebang removal in Input Format; it can link to Shebang for a description of what a shebang is, its grammar, etc.

This follows the pattern that we'll similarly be using for frontmatter.

cc @ehuss

In #2192, we extended our documentation about
shebangs but kept it in Input Format under a section on shebang
removal.  But really, this section is mostly now about documenting
what a shebang is, for our purposes.

Let's separate this out into a new subchapter.

We'll keep the rule about shebang removal in Input Format; it can link
to Shebang for a description of what a shebang is, its grammar, etc.

This follows the pattern that we'll similarly be using for
frontmatter.
@rustbot rustbot added the S-waiting-on-review Status: The marked PR is awaiting review from a maintainer label Mar 4, 2026
~LF* (LF | EOF)
```

r[shebang.intro]
Copy link
Contributor

Choose a reason for hiding this comment

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

Is there a reason the intro was moved to be below the syntax?

Generally I'd like to move to an outline where sections are generally organized so they start with an introduction, then have the syntax, then key behaviors and rules, and then more minutia like restrictions.

I realize there are big sections of the reference that still have the syntax first, but I would prefer to move to this style.

Copy link
Contributor Author

@traviscross traviscross Mar 5, 2026

Choose a reason for hiding this comment

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

No reason other than, as you say, matching similar nearby chapters. I had similarly considered it both ways. I'll move it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

S-waiting-on-review Status: The marked PR is awaiting review from a maintainer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants