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

Tabs vs Spaces -- The blind remix. #158

Closed
dlikhten opened this issue Feb 19, 2020 · 8 comments
Closed

Tabs vs Spaces -- The blind remix. #158

dlikhten opened this issue Feb 19, 2020 · 8 comments

Comments

@dlikhten
Copy link

No description provided.

@dlikhten
Copy link
Author

Is it possible to add an option for tabs vs spaces. Some engineers with vision problems (different kinds) really find changing the tab-width of their editor helps significantly.

Curious if this is a strong enough problem to warrant a flag, or a fork.

@dlikhten dlikhten changed the title Tabs vs Spaces -- Tabs vs Spaces -- The blind remix. Feb 19, 2020
@dgutov
Copy link

dgutov commented Mar 26, 2020

Sounds like a good cause for an editor plugin (to display indentation differently) rather than a reason to change how to file is saved on disk. Your team probably has different kinds of engineers.

@dlikhten
Copy link
Author

Isn't that literally the purpose of tabs? Characters that can be displayed differently based on people's editor preferences?

@dgutov
Copy link

dgutov commented Mar 26, 2020

It differs. People and editors use tabs in a variety of ways.

E.g. the GNU project historically used a mixture of tabs and spaces to "save disk space". In that scheme you could have one tab character per several indentation levels.

@dlikhten
Copy link
Author

Okay I will be very clear: I am in absolutely no way advocating for Tabs being used for saving bits. Nobody cares about that.

You're right historically tabs have been used differently.

My question was: Is accessibility a worthwhile reason to make it an option, or is it more appropriate to make a fork?

@schpet
Copy link

schpet commented Jun 6, 2020

FWIW i'm able to use rubocop with standard's rules as described in #30, using tabs instead of spaces with the following .rubocop.yml:

require:
  - standard/cop/semantic_blocks

inherit_gem:
  standard: config/base.yml

Layout/IndentationStyle:
  Enabled: true
  EnforcedStyle: tabs
  IndentationWidth: 1

Layout/IndentationWidth:
  Width: 1

this means i run bundle exec rubocop and not bundle exec standardrb

@natecox
Copy link

natecox commented Jun 9, 2020

I was presented with this earlier and it pretty much instantly changed my opinion of the tabs vs spaces debate: https://www.reddit.com/r/javascript/comments/c8drjo/nobody_talks_about_the_real_reason_to_use_tabs/

For the first time ever I'm advocating for using tabs as a community standard, to better support members of that community.

@jmkoni
Copy link
Contributor

jmkoni commented Jan 22, 2021

Unfortunately, we aren't going to switch to tabs because that is not the community standard. However, @schpet brought up a great solution if you need to use tabs in your project but still want to use the rest of Standard 😄 #158 (comment)

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

No branches or pull requests

5 participants