notes

Technical notes ...
Windows ...
You might want to use windbtp spy++ and procexplored to debug on windows

windbg is command line debugger, it's in windows kit directory , example 
"c:/Program Files (x86)/Windows Kits/8.0/Debuggers/x64/windbg.exe"  alview.exe 

procexp.exe and spy++ for debuging is good

"winwacky" stuff is wraps from winapi (win32)  to posix forms 
Linux ..

valgrind and gdb are tools used to debug alview on linux.

___ 
git commands ...
# review your changes
git status

# commit the changes
git commit -m "Decription of my change"

# push them back to the remote repository
git push origin master

git push origin master --force

git remote add origin
git push origin master https://github.com/NCIP/alview.git

git pull https://github.com/NCIP/alview.git
git commit -m "latest changes"
git push https://github.com/NCIP/alview.git

#initial
touch README.md
git init
git add README.md
git commit -m "first commit"
git remote add origin https://github.com/NCIP/alview.git
git push -u origin master

git fetch --all
git reset --hard origin/master
git push https://github.com/NCIP/alview.git


# FORCE UPDATE ...
git push origin master --force
git push https://github.com/NCIP/alview.git --force

#force command line not gtk/X on linux ...
unset SSH_ASKPASS
#windows refuses to respect execute permisstion fix ... (test this more)
git update-index --chmod=+x   go

___
final checklist
1) turn off debug.