-
Notifications
You must be signed in to change notification settings - Fork 1
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
Interferes with doc block style comments #3
Comments
This ties in with auto-indentation when entering a new line. Unfortunately there is currently no way to retrieve document language information from the VSCode extension API, so I'm not sure how to get the necessary information to allow this sort of behavior. This issue may have to remain open until such a VSCode API feature is implemented. |
I hope we can find a way in the future to enable this. In my example the behaviour I get with my |
As a workaround, could you add a configurable field for file extensions where this plugin would be disabled or is that also an information we cannot access in vscode? |
@cb109 What you can do is disable the extension by default, and enable it only for specific workspaces (right-click the extension and select "Enable (Workspace)" while the workspace is open). I'll take a look to see if I can enable/disable it based on the current document language, but that might run into the limitations mentioned here. |
This extension is great for using tabs for indentation while aligning comments white spaces, however it interferes with features that automatically continue comment blocks on pressing Enter.
Say
>
is the position of the text cursor and·
is a space character...Pressing Enter to insert a new line no longer does this:
Instead it only does this:
The text was updated successfully, but these errors were encountered: