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

Don't create empty .vscode subdirectory #253

Closed
bialix opened this issue Nov 17, 2017 · 3 comments · Fixed by #264
Closed

Don't create empty .vscode subdirectory #253

bialix opened this issue Nov 17, 2017 · 3 comments · Fixed by #264
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@bialix
Copy link

bialix commented Nov 17, 2017

Environment data

VS Code version: 1.18.1
Python Extension version: 0.8.0
Python Version: does not matter
OS and version: Windows

Expected behavior

Don't create empty .vscode subdirectory. It's annoying. If your extension needs something and that ain't there - don't create empty directory. I don't need this directory. I don't have to change some default options just to stop your extension to doing the right thing. Your extension by default should not mess my disk without the reason. There is no reason for this.

Stop creating empty directories.

@DonJayamanne
Copy link

This is possibly due to the fact that the extension is attempting to generate a .tags files for workspace symbols (used in code navigation). Looks like you do not have ctags installed.
This can be turned off in your user settings as follows:

  1. Go into user settings
  2. Add the following setting:
"python.workspaceSymbols.enabled": false

Please let me know if this resolves the issue, if not please provide the instructions required to reproduce this issue (e.g. does it happen when you open a python file, open a workspace, when debugging, etc)

@DonJayamanne DonJayamanne added info-needed Issue requires more information from poster feature-code navigation labels Nov 17, 2017
@bialix
Copy link
Author

bialix commented Nov 20, 2017

Sorry, but for me this inappropriate solution. I don't want to remember about this strange option every time I install your extension on some new computer I work on.

I've been using VScode and your extension for about year or maybe 2, I don't remember exactly. And then all of a sudden around the summer 2017 I've noticed this strange behavior that your extension started to create empty folders. I've already filed a bug report https://github.com/DonJayamanne/pythonVSCode/issues/1096#issuecomment-317409894 but you closed it. Feel free to close this one,

I just want to comment on this bad behavior of your extension. It wasn't created any empty folders in the past, I see no reasons for me to continue using your extension just because my computer don't have ctags installed (as most of Windows computers I guess). I probably don't need your extension if first thing I should do after install it - if I should disable linters, ctags and so on and so on. Probably your extension is great for other people, but I just need to edit my python project without worrying about all this stuff I don't need and don't care about. Sorry, but it seems your extension is just too much for me.

I'm really interested to use something that should help me in my work on python project, but I don't need all this stuff, remember of some bizarre options I should edit in json settings and so on. It wasn't always this way, but now it's stopper for me. The most bizarre thing is that Microsoft now endorses your extension.

Sorry, I simply uninstalled your extension and now I should remember only one thing: don't install it on other computers I work on.

Sorry again.

@DonJayamanne DonJayamanne added awaiting 1-decision and removed info-needed Issue requires more information from poster labels Nov 20, 2017
@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Nov 20, 2017
@DonJayamanne
Copy link

DonJayamanne commented Nov 20, 2017

@bialix I agree with you. And I'm sorry about the trouble this issue may have caused.
Also, I agree, the folder shouldn't be created when the extension gets activated.
The next version of the extension will not create this directory.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants