When I write vim in powershell or cmd it say that "path/to/my/old/portable/vim80/vim.exe" does not exist. I have removed that vim long ago and have deleted its path from path variable.
I tried adding the path of the new portable vim to the path variable, but Windows still somehow finds the old path. I can't for the life of me figure out where Windows is reading that path. I looked under registry too to no avail. Even ran Ccleaner on the registry and still the problem persists.
Any help is appreciated.
Thank you very much
TLDR; Somehow windows cannot forget the path of my old vim. I added the new path, but still it picks up the old one, how do I replace the old path? How is windows still finding the old path?
Related
I am opening a project in Visual Studio Code and it can't find npm, in spite of NPM being in my system path.
If I open a command prompt or a powershell prompt, and I type env I See it in my path. If I open a terminal in VS:Code and type env it omits both: /d/nodejs and /c/Program Files/Azure Data Studio/bin from the list of items in my path.
I have tried rearranging all of my paths in my Windows Environment Variable editor dialog, and no matter the order, only these two items are missing. So, I have validated that it is not other paths that could be causing issues in some sort of path parsing code.
Why would Visual Studio Code alter my path environment variable, removing node and its own path from the environment variable list?
If I move these items from my system path to my user path, it is able to find them but there are some other subtle issues with things not being found I haven't been able to figure out yet.
Note: These are the ONLY two items being removed. And they are ONLY removed in VS:Code.
Even though there is other weirdness with moving the path to my user path from my system path, that was able to be worked around. So, my answer is: Move your nodejs path from your system path in Windows to your user path in Windows.
So, I've downloaded the .zip 1.32.11 Windows x64 release from the Dart-Sass's Github repo and extracted it to the Program Files folder. Using the steps provided, I found Path under System variables in Step 4. There was no PATH there, the closest thing was PATHTEXT and Path. My first question: Can I use Path or I have to create a new System variable called PATH. Thinking Path was sufficient, I decided to edit the System variable and then press Browse to search for the Dart-Sass folder. After this was done, I went to Command Prompt and typed sass -version. The result was that Sass was not recognized. Did I do anything wrong? If so, what can I do to fix it?
I'm noticing two things about your problem. The first is your path variable... did you make sure to change Me to your username in the PATH variable?. The second encompasses your installation. Can you find the dart *.exe file? If not, try uninstalling and reinstalling, making sure each step is completed word for word.
I am trying to Run setup.exe as part of Oracle 19c installation on windows 10.
I have downloaded the zip file and extracted it in a folder inside C drive.
When I try to run setup.exe by right click and run as administrator option, a command prompt just flashes for a split of a second and nothings starts after that.
I have found the solution:
After extraction, rename the extracted directory to db_home
Move the db_home directory to the root of your Hard Drive ( in my case its C:\db_home )
run setup.exe as an administrator.
You will see a cmd window pop up and then the red window with the Oracle symbol in it.
Do NOT skip step 2nd step as that is how I was finally able to get it to install.
This also worked with 19c.
I also faced the problem. After seeing this thread, in a while, I figured it out. Apparently, keeping the db_home folder inside a folder that has space in its name caused me the same issue.
I had the same problem and read something about problems with extremely long paths in packages and using the native Windows unzip utility. I unzipped the package using 7-zip instead and it solved the problem.
I was trying to install from d partition and does not work. Then I just move all the installation folder to c partition and it works fine.
I'm an Oracle DBA and I don't know when the change happened or what the source of issue is, but when installing the Oracle client you can no longer have a space " " in the path for the Oracle setup.exe file.
It doesn't matter what utility extracted the files or what drive or path is used (except there is and always has been an issue with very long path names) - it just cannot have a space in the path.
I hope this helps.
This issue has a simple solution:
When we run the Setup file we see a flash CMD in the background...
Your System Environment variable path(DB home) has Space in it.
It should be no space(db_home)
This personally works for me to install.
I accidentally ran a script that changed how my terminal (macOS Sierra) looked by completely changing all the code in .bash_profile getting rid of the Python paths as well. I would like to know if it is possible to find the previously saved version of .bash_profile so that I can revert to it.
EDIT: I had been looking at the hidden files in my home directory when I noticed that Anaconda had made a backup file: .bash_profile-anaconda.bak that had most of all of my code at the time I installed Anaconda. It may not solve all the problems but it partly works. Thanks Gordon Davisson for mentioning Time Machine as I didn't consider that even though I backed up my computer the day before.
No copy of .bash_profile is made. You need to find in backups if you have any.
I just started a new job, and I've installed vim and gvim on the machine. I'm trying to get my .vimrc working, I've placed it in the directory that %USERPROFILE% points to, but vim isn't picking it up.
But while %USERPROFLE% does point to C:\users\<me-name> I've noticed that My documents are stored on an external share somewhere.
The share is also mapped...and I've tried putting .vimrc out there to, to no avail.
Is there some other place I can put .vimrc ?
In windows, the .vimrc file is stored as _vimrc
For more information Refer: http://vim.wikia.com/wiki/Open_vimrc_file
It has all the information you need and more.