You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Github really needs to support per-repository (and per-gist, and probably others) configuration for indentation (e.g. tabs vs spaces, indent width).
Sure, you can set your preference for yourself, as a viewer of things like source files. But code is written by an author with specific indentation settings, and likely won't look right with any other. The file needs to dictate the configuration, not the viewer.
I propose Github add per-repo and per-gist settings for how tabs in files should be interpreted, and what the default should be for a new file created via the web UI.
A newly-created repo should default to whatever the creator's preferences are.
And if you want to get really fancy, you'd have per-language (or per-filename extension) configuration (e.g. YAML really needs to be two spaces, but my Swift code is always 4-space tabs).
I currently can't author a Gist and then send it to someone without tediously adding ?ts=4 to the URL. What they git might be a complete mess without that.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
Github really needs to support per-repository (and per-gist, and probably others) configuration for indentation (e.g. tabs vs spaces, indent width).
Sure, you can set your preference for yourself, as a viewer of things like source files. But code is written by an author with specific indentation settings, and likely won't look right with any other. The file needs to dictate the configuration, not the viewer.
I propose Github add per-repo and per-gist settings for how tabs in files should be interpreted, and what the default should be for a new file created via the web UI.
A newly-created repo should default to whatever the creator's preferences are.
And if you want to get really fancy, you'd have per-language (or per-filename extension) configuration (e.g. YAML really needs to be two spaces, but my Swift code is always 4-space tabs).
I currently can't author a Gist and then send it to someone without tediously adding
?ts=4
to the URL. What they git might be a complete mess without that.Beta Was this translation helpful? Give feedback.
All reactions