Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve tabSize configuration based off file types [Feature Request] #18084

Closed
rajinder-yadav opened this issue Jan 4, 2017 · 2 comments
Closed
Assignees
Labels
config VS Code configuration, set up issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@rajinder-yadav
Copy link

What exist today is very limited, a one size fits all don't work for most people:

  "editor.tabSize": 4,

A suggested improvement:

  "editor.tabSize": {
     "default": 4,
     "web": 2,
     "cpp": 3
   }

   // Don't need to specify the '.' before extension name.
   // Specify multiple extensions with '|' or separator.
   tabFileExtensions: {
    "cpp": ['h|hpp|c|cpp|cc'],
    "web": ['js|html|css|ts']
   }
@rajinder-yadav rajinder-yadav changed the title Improve tabSize configuration based of file type [Feature Request] Improve tabSize configuration based off file types [Feature Request] Jan 4, 2017
@sandy081 sandy081 self-assigned this Jan 4, 2017
@sandy081 sandy081 added workbench config VS Code configuration, set up issues labels Jan 4, 2017
@sandy081 sandy081 added this to the January 2017 milestone Jan 4, 2017
@sandy081
Copy link
Member

sandy081 commented Jan 4, 2017

We are planning to implement file based configurations in which this will be covered

@sandy081
Copy link
Member

Duplicates #1587

@sandy081 sandy081 added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 23, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
config VS Code configuration, set up issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants