Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 hours ago.
Improve this question
I have a powershell script that runs perfectly in powershell 7 terminal in vscode. When I try to run it in the vscode window debugger, it generates an 'invalid syntax' error on any powershell variable in the script (like $ex)! The Microsoft Powershell extension is installed. It seems like the Powershell extension is not working... what could be wrong. All other languages work fine (python,javascript C++, etc).Alsoran the same powershell script successfully in powershell command window. uninstalled vscode and reinstalled. uninstalled powershell extension and reinstalled.
Related
I am a beginner programmer who has started using VScode a few weeks ago. Today I noticed that my intellisense extensions were not available. I use tabnine and kite.
another problem was that when I wanted to execute a python script nothing happened. the terminal didnt respond and even after reloading several times nothing happened.
i am using windows 10
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
I am using the Fish shell (version 3.3.1) on MacOS. Every time I run a command it shows this error multiple times:
error: Unable to open universal variable file '/': Permission denied
The commands still run perfectly, but it's very annoying to see these errors. They are still on the screen even after a clear command.
Fish has a feature where it'll store so called "universal" variables to a file on disk, so they can easily be persisted and shared among open fishes.
This error:
error: Unable to open universal variable file '/': Permission denied
Shows that fish is trying to open the file at "/", the root of the filesystem. This points to a misconfiguration, because "/" isn't a file, by definition. It's a directory.
The file is supposed to be in the config directory, which is at:
$XDG_CONFIG_HOME/fish, if that variable is set
$HOME/.config/fish, if it isn't
I can't find the specific sequence to reproduce this, but it appears that $XDG_CONFIG_HOME or $HOME are set when fish is started (by its parent process, probably the terminal), and to non-functional values.
Was having this same issue after installing using brew install fish.
What finally worked was uninstalling fish.
brew uninstall fish
Then removing fish from my .config folder.
cd ~
rm -rf .config/fish
Then I just installed fish using the fish GUI installer.
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 3 years ago.
Improve this question
Flutter doctor command doesn't work on Visual studio Code terminal?
flutter doctor work on terminal full path but dose not work on VS code terminal or another path on pc?
You need restart your computer after edit environment path
You need to have each path on separate line. That's what I have.
click NEW and then enter your path like below
C:\src\flutter\bin
Then restart
Edit: I would suggest you add your git and all the other paths also on separate line. you should be very careful with environment variables.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 years ago.
Improve this question
I have been trying to learn C recently. I've been using VS Code and run into a big problem. The start menu does not show a Developer Command Prompt and so I can't compile the code. I have searched everywhere for this program, I don't even have a folder named "Microsoft Visual Studio" under my Program Files (x86). I already tried reinstalling the software and nothing changes.
My problem: I can't find the VS Developer Command Prompt, which I would like to use to compile my code.
VSCode is much more light-weight and is, in essence, a completely different product. VSCode doesn't ship with a complete setup of MsBuild and of the compiler frameworks that ship with the full version of Visual Studio. You can install these alongside VSCode if You need them by installing "Build Tools for Visual Studio 2017", you can find the installer all the way at the bottom of the Visual Studio download page.
With these tools installed, you should be able to build your code. I'm not 100% convinced this will bring back the Visual Studio Developer Command Prompt, but what this command prompt has which makes it work, is a number of pre-configured path statements to the right version of msbuild.exe and locations of other tools required to compile a .NET application. Manually configuring your user's PATH environment variable should work as well, after installing the right set of tools and SDKs.
Some variables that you may depend on, like:
VCIDEInstallDir=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\
VCINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\
VisualStudioVersion=15.0
VS150COMNTOOLS=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\
VSCMD_ARG_app_plat=Desktop
VSCMD_ARG_HOST_ARCH=x86
VSCMD_ARG_TGT_ARCH=x86
VSCMD_VER=15.5.3
VSINSTALLDIR=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\
VSSDK150INSTALL=C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VSSDK
Have no direct equivalent in VSCode. If you are reliant on these, you'll need to also install Visual Studio (Community | Pro | Enterprise) on the same machine, or you will need to change your build scripts to break this dependency on items that are specific to the Visual Studio IDE.
I am not sure for what purpose you need vs command prompt but
There is developer terminal for visual studio code, you can access it through, view -> Integrated Terminal or ctr+`
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question 23 days ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I am using XMing to run Emacs from WSL, which is working quite well. My issue is when trying to share folders between Windows and WSL. I have tried the following:
Project located in the Windows file system, accessed via /mnt/ in WSL
Symlink (created in WSL bash) of project located in the Windows file system
Copy the project to the WSL file system
Out of the 3 listed options, only the last works with projectile (and likely other Emacs packages). But I need to be able to access/modify the files from Windows as well, so that is not a viable option.
Has anyone found a good solution for this?
I do it so (also to sync between Windows_laptop & Ubuntu_pc):
I have folder "workspace"
and symlinks to it: windows symlink under win and linux symlink under linux.
%USERPROFILE%\Cloud\workspace
for Win usage:
made windows symlink: %USERPROFILE%\workspace -> %USERPROFILE%\Cloud\workspace
for Ubuntu usage (WSL):
made linux symlink: ~/workspace -> /mnt/C/Users/USER/Cloud/workspace
May this help?
One of the advantages of WSL (windows subsystem for Linux) is that you can share files easily with your windows.
I have used the below codes with WSL Ubuntu (but this should work with other versions of Linux as well). Using /mnt will do all the magic.
Syntax:- cd /mnt/drive/Folder/Subfolder
Sample code:- cd /mnt/c/Users/Saswat