I have been using Git-1.8.3 from a flash drive successfully from both work and at home on win7 machines. Yesterday I noticed that when I try to open git-bash at home, the window flashes open and disappears instantaneously. I don't see an error message. Thinking the file may be corrupted, I tried it at work and it opens normally. Are there any logs that I can check to at least get an error message on what is happening?
Try downloading it again? If that doesn't work can you give the file name and location you are using for git bash?
Related
So I've been running into an issue when running a local expo-webpack server on Windows. Sometimes I get a few changes sometimes only one change on a file then I get this error EPerm cannot perform operation, lstat with the filename and a ~ afterwards.
I've tried to change security permissions to no avail. It seems to be a windows only problem as far as I can tell because when running in WSL it works as well as on a separate mac machine. I also removed read-only but after I check again it says read-only again. I also tried the version of node that works on WSL.
Sometimes when i open the msys2 mingw64 bit terminal an error is displayed in console:
Error: Could not fork child process: There are no available terminals (-1).
This error oqurues many time during the project time, but if i restart the laptop, there is no error.
Anyone who has facing simillar error?
I have seen this issue too, and it disappears after reboot.
Make sure you have run autorebase.bat in the msys64 folder.
When I open the file I downloaded from https://git-scm.com/download and then Windows, nothing happens. I've tried running it as a normal user and administrator but nothing happens. Not even a processor in the Task Manager opens.
What could cause this? Is it because Git hasn't been updated for Windows 10 yet, or is it something else? I just did a clean install of Windows 10.
Perhaps, you could try chocolatey (even if I'm not sure it will change something...) :
https://chocolatey.org/packages/git
Or the RC for the next to be released git for Windows :
https://github.com/git-for-windows/git/releases
Try running the installer from command prompt.
More details
This is what just happened to me. When double-clicked, or even ran as admin, Git-2.34.1-64-bit.exe shows this. None of those 3 buttons work.
The only thing that helped was running the file from command prompt.
This is a weird one.
Update
A similar thing just happened again with node-v17.3.0-x64. This time, I would get this screen even when running from command prompt.
But it would work just fine if the cmd.exe is ran as an administrator.
It's maddening.
I'm having some issues trying to open up Atom in my terminal. I know I can open it manually but I'm trying to figure out what exactly is the issue.
This is what I'm getting when I try to open Atom in my Terminal.
Cannot locate Atom.app, it is usually located in /Applications. Set the ATOM_PATH environment variable to the directory containing Atom.app.
Anyone have an idea as to what the issue is???
If your application is called "Atom 2" or something, try this:
Open /usr/local/bin/atom
Change the line ATOM_APP_NAME=Atom.app to something like ATOM_APP_NAME='Atom 2.app'
lets get this fixed for you.
The error you're getting is indicating Atom isn't located where it should be, which is the Applications folder. Open up Applications and confirm it isn't there. If it isn't, locate where Atom is on your computer and drag it into the Applications folder. If you have Atom and Terminal both open, restart them. Then try opening Atom from the Terminal.
-bash: sencha: command not found
I just spent a few hours trying to make this Sencha Cmd works on my MacBook, but just couldn't. I uninstalled a previous version and just couldn't get it to work again. I always get the
-bash: sencha: command not found
error. I did try everything in this post, without success.... I even get an error when I call
.bash_profile
stating that it's not found... Do you have any idea what could be the problem ?
I'm fairly new to the Linux command world so I might miss a point here. Maybe I might use "sudo" to be granted acces to bask_profile ?
EDIT : I got it working for the current bash session. I position myself at the user root (~/) and call ". .bash_profile"(the space is important here). BUT... it only works for the current session. As soon as I close Terminal and reopen it, I loose everything :-(
OK, just so you know, I managed to fix the damn thing be opening and editing the ".bash_profile" file in a text editor (TextMate for me). This is an hidden file, but you can configure your Mac to show those files in Finder. The file is located at your user's root. It is quite annoying to have to spend hour messing in path and environment variables in 2013... Installer should do those things and reports error if something happens in the install process.