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

Tab key should be mapped to 2 spaces #4

Open
lucatrv opened this issue Jun 22, 2018 · 5 comments
Open

Tab key should be mapped to 2 spaces #4

lucatrv opened this issue Jun 22, 2018 · 5 comments
Labels

Comments

@lucatrv
Copy link

lucatrv commented Jun 22, 2018

According to the Nim Style Guide, two spaces should be used for indentation of blocks, so IMHO the "tab" key should be mapped to 2 spaces instead of 4.

@lucatrv lucatrv changed the title Tab key should add 2 spaces Tab key should be mapped to 2 spaces Jun 22, 2018
@genotrance
Copy link
Owner

Snip actually supports multiple programming languages so I just set it to 4 spaces by default. You can always change it with keymap.txt:

TAB = TO_2_SPACES

@lucatrv
Copy link
Author

lucatrv commented Jun 22, 2018

Well... in my opinion most people are going to use snip as a Nim local playground, so it would be better to set 2 spaces by default (and change it for other languages), but never mind of course.
Thanks

@bevo009
Copy link

bevo009 commented Jun 26, 2018

Just to add...the Nim Playground has a default of 4 spaces, so it is consistent with that :)
I notice a fair few Nim users using 4 spaces also

@lucatrv
Copy link
Author

lucatrv commented Jun 26, 2018

Instead of conforming to Nim Playground, IMHO both should be updated to conform to the Nim Style Guide.

genotrance added a commit that referenced this issue Sep 8, 2018
@genotrance
Copy link
Owner

Fixed in #head - please try out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants