Repository navigation
formatOnType will change two spaces before comment to one #1763
Description
Environment data
- VS Code version: 1.23.1
- Extension version (available under the Extensions sidebar): 2018.5.0-rc
- OS and version: MacOS 10.13.4
- Python version (& distribution if applicable, e.g. Anaconda): CPython 3.6.5
- Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
- Relevant/affected Python packages and their versions: XXX
Actual behavior
a = 1 # two spaces before hash sign
<enter>
a = 1 # one leftExpected behavior
keep two spaces.
BTW, I notice this feature is being considered for deletion (#1586), is this kind of issues welcome?
Steps to reproduce:
- XXX
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
XXX
Activity
brettcannon commentedon May 29, 2018
Yep, this info is still welcome as we're re-evaluating whether to keep or remove the feature so bug reports like this are still useful.
brettcannon commentedon May 29, 2018
PEP 8 says to use two spaces from the statement.
MikhailArkhipov commentedon May 29, 2018
Missing Link (@MisLink) - yes please. This one is trivial to adjust. Do you have the feature on a regular basis?
MisLink commentedon May 30, 2018
well, use frequency of inline comments is very low for me.
MikhailArkhipov commentedon May 30, 2018
I meant the feature itself (i.e. format on type) :-)
MisLink commentedon May 30, 2018
oh sorry, I misunderstand your meaning...
I take this feature as my default global setting.