Skip to content

Conversation

@MythreyaK
Copy link
Contributor

Add config documentation for HeaderInsertion, introduced in this PR.

Also added a commit for the default sample block. If this needs to go in a separate PR, let me know!

Copy link
Contributor

@HighCommander4 HighCommander4 left a comment

Choose a reason for hiding this comment

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

Thanks for the doc patch. Looks good with two corrections.

config.md Outdated
Completion:
AllScopes: Yes
ArgumentLists: FullPlaceholders
HeaderInsertion: Never
Copy link
Contributor

Choose a reason for hiding this comment

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

I assume by "sample block (default)" you mean that you want to list the defaults here.

The default for HeaderInsertion is IWYU.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah whoops! Fixed it.

config.md Outdated
the delimiters are `<>`.

### HeaderInsertion
{:.v20}
Copy link
Contributor

Choose a reason for hiding this comment

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

This config option will actually first appear in clangd 21. (llvm 20 has branched in January, so any commits more recent than that target llvm 21 unless they are explicitly backported to the llvm 20 branch.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah I didn't realize, 20 had already released, thanks! Should be fixed now.

@HighCommander4 HighCommander4 merged commit ef23380 into llvm:main Apr 23, 2025
@MythreyaK
Copy link
Contributor Author

I just now noticed that the default blocks use 2 spaces for indent, whereas my commit has 4 😅 . Should I update the PR with a fix, for consistency?

@HighCommander4
Copy link
Contributor

Should I update the PR with a fix, for consistency?

Sure (but note that you can't reopen a merged PR, you need to submit a new one)

@MythreyaK
Copy link
Contributor Author

Done, sorry for the trouble and thank you for your time!

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