-
Notifications
You must be signed in to change notification settings - Fork 17.4k
Add new editor.tabType scoped setting #3719
Comments
Thanks @lee-dohm that's exactly what I was looking for. |
Removing from the API freeze roadmap as it is not necessary for the api freeze. Will happen shortly after. |
Also please add support for per language soft tabs support somehow. |
+1, I would really appreciate a fix! |
+1 This soft tab issue is pretty annoying... |
👍 We need this |
👍 Really hard to work in indentation-sensitive languages when suddenly Atom inserts spaces instead of tabs. |
Not really sure how such a critical issue didn't make it for 1.0. Shame on Atom for still not being able to manage spaces/tabs |
👍 I find myself having to replace all tabs with spaces and re-open a file to get tab to insert spaces properly, which isn't very intuitive. |
This should be made possible language specifically. Most languages have their own coding conventions. This is a critical bug if you ask me. |
👍 Can't even think of switching to Atom for actual work until this is fixed. |
+1 |
1 similar comment
+1 |
All the +1's only add noise at this point, so I'm locking this issue until someone begins working on it. At that point we may re-open it for discussion purposes. |
Behaviour of tabType functions is discussed on issue atom#3719. Also, introduce userTabTypeOverride variable which hold temporary user preference on current editor.
Most reports of issues seem to be closed without resolving the underlying problem. There is only one open I could find (on cursory clicking): Closed
OpenThe big issue as reported is the inaccurate "guessing" combined with the inability for an editor-wide setting (and not per-file setting). It may be that several preferences may be required instead of having one monolithic setting which is clearly causing unhappiness:
The idea would be to be able to re-order these in terms of priority, based on the needs of the user. |
I'm with @jeffmcneill on this one; it's still a problem in Atom 1.16.0 and the current settings just doesn't work. The editor-settings package outlines a lot of the functionality I would like to see in Atom wrt. whitespace handling, but it also does not work correctly as it seems to be fighting with Atom on what tab type should be used. Couple that with the whitespace package and you have complete chaos. I would love to see the current settings, packages and everything related to whitespace wiped from the face of the earth, because it's bug-ridden junk that Just Doesn't Work. Then, I would like to see something implemented along these lines:
With these three levels all supported within Atom without any packages, I believe it's possible to reach sanity and get rid of a lot of bug-ridden, "intelligent" code that obviously doesn't work and also serve the needs of most people. |
This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks! |
While digging into scoping
editor.softTabs
in #3718, it's pretty clear that the setting has very little influence on the actual value chosen. It's effectively the worst-case fallback: it only works on an empty file.I propose doing a couple things:
editor.tabType
setting that accepts 3 values: Auto, Hard, Soft. With the default beingauto
. Then in the scoped settings for each language, they can set it to whatever they want.TextEditor::setSoftTabs
to being a settings override accepting 4 values: unset / use-the-settings, Auto, Hard, SoftSee
atom/src/text-editor.coffee
Line 93 in 4231d69
atom/src/text-editor.coffee
Line 2319 in 4231d69
Refs
Comment if you know of more issues, complaints. I know there have been several complaints about this, but cant find issues.
The text was updated successfully, but these errors were encountered: