Skip to content
This repository has been archived by the owner on Mar 3, 2023. It is now read-only.

Atom keeps failing at inserting a <tab> #4050

Closed
alexandernst opened this issue Nov 4, 2014 · 7 comments
Closed

Atom keeps failing at inserting a <tab> #4050

alexandernst opened this issue Nov 4, 2014 · 7 comments

Comments

@alexandernst
Copy link

I have Atom .141 and softTab disabled, and yet hitting the TAB key will insert N spaces instead of a TAB character.
Even further, Atom doesn't care at all if the entire file is TAB-indented, it just keeps inserting spaces.
This is a completely must-fix before a 1.0 release.

Short video showing the bug: http://youtu.be/JWAH-7fqYzo

@thomasjo
Copy link
Contributor

thomasjo commented Nov 4, 2014

Are you able to reproduce this in safe mode? atom --safe

@alexandernst
Copy link
Author

This get's fixed when Atom is running in safe mode

@thomasjo
Copy link
Contributor

thomasjo commented Nov 4, 2014

Then this issue is caused by a third-party package. Are you using emmet or autocomplete-plus? They are known for interfering with tab keybinding.

@alexandernst
Copy link
Author

Not sure what happened, but after running atom --safe and then running only atom I can't reproduce the bug anymore. Is --safe cleaning some Atom files? Or maybe changing permanently some config option?

@thomasjo
Copy link
Contributor

thomasjo commented Nov 4, 2014

It might perhaps alter some data in ~/.atom/storage. Maybe @benogle, @kevinsawicki or @nathansobo have some insight into what might have been happening. Old "tab style guess" that got unstuck?

@alexandernst
Copy link
Author

I'll close this bug as it was some fauly config on my side. Reopen if you feel there is a need for further investigation and I'll reply to all your questions.

@lock
Copy link

lock bot commented Jan 25, 2019

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!

@lock lock bot locked as resolved and limited conversation to collaborators Jan 25, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants