You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am using the VisualStudio Code extension Better Comments, which works by coloring comments based on a specific symbol/string right after the comment start. The frustrating part is that Black always adds a space in between, which would turn this:
a=10#? Should we change this
into this:
a=10# ? Should we change this
which looks disgraceful.
Describe the solution you'd like
Some setting for an array of characters that can extend the commen start e.g. `--comment-start '["*", "!", "TODO"]'
Describe alternatives you've considered
Another option would be a flag to turn of formatting a space after the comment start.
The text was updated successfully, but these errors were encountered:
I too would like an option to control this behavior, but probably more to just disable it entirely. I find that having the space is good for prose, but requiring it for disabled code feels wrong/unnecessary, and enforcing this automatically is probably not possible.
Is your feature request related to a problem? Please describe.
I am using the VisualStudio Code extension Better Comments, which works by coloring comments based on a specific symbol/string right after the comment start. The frustrating part is that Black always adds a space in between, which would turn this:
into this:
which looks disgraceful.
Describe the solution you'd like
Some setting for an array of characters that can extend the commen start e.g. `--comment-start '["*", "!", "TODO"]'
Describe alternatives you've considered
Another option would be a flag to turn of formatting a space after the comment start.
The text was updated successfully, but these errors were encountered: