Plugin breaks the "use_tab_stops" option

[sccolbert]

From the default sublime settings files:

    // If translate_tabs_to_spaces is true, use_tab_stops will make tab and
    // backspace insert/delete up to the next tabstop
    "use_tab_stops": true,

When this plugin is enabled, that option does not work. When this plugin is disabled, the option is honored.

[zhengbli]

Can you elaborate what exactly is not working?

I tried it on my machine, and got the following behavior:

Is it different from what you expected? Thanks!

[sccolbert]

If you have translate_tabs_to_spaces set to true, then when use_tab_stops is true, pressing backspace at the point where a tab was inserted will (should) remove all the spaces inserted for that tab, instead of just a single space character.

For example, if you open a brace and press enter, the next line will auto-indent. Pressing backspace once should remove all spaces inserted for the indentation, instead of only a single space.

When this plugin is installed, that behavior does not work.

[steveluc]

This is a known problem. The issue is that Sublime does not report the buffer changes it makes when it applies its algorithm to backspace. Therefore we don't know what has changed in the buffer. We haven't found a way yet to support this setting. We did just find a way to support any setting for translate_tabs_to_spaces and we are optimistic we'll find a way to efficiently support use_tab_stops. That is the last remaining setting that we haven't been able to find an efficient solution for (we don't think sending the entire buffer on every backspace is an efficient solution).

[sccolbert]

@steveluc thanks for the update. I agree about not sending the entire buffer on every backspace.

[bartzy]

Is this fixed yet? Because I still encounter this issue.

Thanks!

[zhengbli]

@bartzy this is not fixed yet. We will come back to this, though the team is currently short of resources to do this quickly. I'll let you know ASAP a fix is merged in, btw a PR is always welcomed :)

[bartzy]

@zhengbli Great, thanks!

It's a small annoyance in a rather bug-free setup :)
Why TypeScript breaks this Sublime behavior though?

[jnu]

Possibly related:

1. odd indentation stuff with copy+paste
   

2. can't paste with cmd-v into new file with TS syntax that hasn't been saved yet
   
   paste from context menu works, only cmd-v doesn't.

edit: both issues only apply to cmd-v paste, not context-menu paste.
edit2: the entire object gets reformatted "correctly" when I type a semicolon if the syntax is otherwise valid.

Any news on this bug?

[jiayihu]

I'm having the same issue, is it still not easily resolvable?

[msieurtoph]

+1.
Any news ?

[jaykyburz]

I'd almost rather run without the plugin.