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

Interferes with doc block style comments #3

Open
Deji69 opened this issue Mar 15, 2019 · 4 comments
Open

Interferes with doc block style comments #3

Deji69 opened this issue Mar 15, 2019 · 4 comments

Comments

@Deji69
Copy link

Deji69 commented Mar 15, 2019

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...

/**
·* Documentation.>

Pressing Enter to insert a new line no longer does this:

/**
·* Documentation.
·* >

Instead it only does this:

/**
·* Documentation.
·>
@j-zeppenfeld
Copy link
Owner

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.

@cb109
Copy link

cb109 commented Aug 26, 2019

I hope we can find a way in the future to enable this. In my example the behaviour I get with my .vue files (html templates) is great, but on the same hand the newline behaviour in Python is now very annoying (no auto-indent). Great extension so far, but kinda unusable with my language combination unfortunately.

@cb109
Copy link

cb109 commented Aug 26, 2019

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?

@j-zeppenfeld
Copy link
Owner

@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.

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

3 participants