Excluding files from your repository Sometimes you may have types of files or folders in your source code tree that you do not want to include in your source code repository. Everyne developing with Visual Studio will immediately know what I mean: VS automatically makes bin and obj subfolders for your project folder in which it puts the buildresults and also creates *.suo files with your personal settings for a solution.
Here’s the situation, you are using bash’s Screen command because you don’t want your flakey internet connection to affect whatever you are working on, and sure enough, the connection drops. Sometimes, when you try to re-attach to this screen session you are told that the screen session is still attached…
~$ screen -r '1234.somescreensession'
There is a screen on:
1234.somescreensession (Attached)
There is no screen to be resumed matching 1234.somescreensession.
How annoying.
UPDATE:
Here is a simple way to take back that screen session.
screen -D -r '1234.somescreensession'
Kudos to Donncha O’Caoimh
Here is a way a longer way to remove the process that is attached to that screen session, so you can reattach to it and continue with whatever you were doing.
ps -ef | grep screen | grep ttytestdev 5760 5688 0 12:31 ttyp1 00:00:00 screen -r 1234.somescreensessionps -ef | grep bash | grep 5688testdev 5688 5687 0 12:28 ttyp1 00:00:00 -bashkill -9 5687Now you should be free to re-attach to this screen session.
Kudos to David Mackintosh
If you are in a position where you want to remove the colossus that is Xcode, here is the terminal command to use.
sudo /Developer/Library/uninstall-devtools –mode=all
In my case, I was using migration assistant to migrate my applications and user account to a new laptop. My older laptop had an older version of Xcode that I didn’t want included in the migration and as it is so big, I didn’t want to take the chance.
Something that has bugged me recently is that when I go to proxy on a particular port, the port is already in use and I get the following error.
bind: Address already in use
channel_setup_fwd_listener: cannot listen to port: 8090
Could not request local forwarding.
Continue reading
This is a super simple command but there is something about the following sequence of characters that I simply cannot retain in my brain.
Continue reading
This is a simple one. For some reason, every time I use the screen command in terminal, I forget the commands.
There are probably lots of cool reasons to use screen but I use it to run a script over a longish period. The advantage of screen is I can start the script in the screen instance and detach from it. I can close my laptop and return later to my terminal, open my screen and check the progress of the script. Also, you can run multiple instances of a script as each screen has its own process.
So the basic commands I use and tend to forget are… Continue reading
