I see the code viewer on Gist honours the tab size preference as well, nice 😊! I've detailed a few things I think could be improved, below.

• The tab size preference would ideally be an indent size preference. Similarly, there'd ideally be an indent style (tabs/spaces) preference. Editors (not viewers) across GitHub and Gist (shown when creating/editing a file in a repo; and creating/editing a Gist) would default to this size and style, unless it's overriden by an applicable EditorConfig.

  • Gist always defaults to 2 spaces at the moment.
  • GitHub editors for new files always default to 2 spaces, even if the applicable EditorConfig specifies indent_style = tab.
  • GitHub editors for existing files correctly detect the indent style. But if the file is tab-indented, they always default to an indent size of 8, disregarding the indent size preference.

• When signed out, the tab size defaults to the browser default of 8. Understandable, because GitHub shouldn't force a specific indent size (wishing browsers had an indent size preference for monospaced fonts hehe). However, if one attempts to change this with a user style that sets tab-size: 4,

  • Tab-indented code blocks in rendered markdown adapt correctly because they're <pre>s.
  • Code viewers initially seem fine 👇 when viewing tab-indented code,
    
  • ...but "break" when a selection is made 👇 because the selectable text is indented with a size of 8 but the shown text is indented with tab-size,
    

When I make "Suggested Changes" and then submit a review, the post-review "Suggested Changes" box does not appear to respect my tab width.

I'm so happy to hear this. 🙏