ignore change on Git
git update-index –assume-unchanged
List all file
git ls-files -v | egrep -r “^h .*”
source : http://stackoverflow.com/questions/16195729/git-list-all-files-with-assume-unchanged-flag
just for fun
ignore change on Git
git update-index –assume-unchanged
List all file
git ls-files -v | egrep -r “^h .*”
source : http://stackoverflow.com/questions/16195729/git-list-all-files-with-assume-unchanged-flag
#!/bin/bash # Target directory TARGET=COPY for i in $(find . -iname *.txt) do mkdir -p "$TARGET/$(dirname ${i:2})" head -100 $i > "$TARGET/${i:2}" done
TOTALCMD#BAR#DATA c:\Program Files (x86)\Beyond Compare 3\BCompare.exe %Z %P %T C:\Program Files (x86)\Beyond Compare 3\BCompare.exe Compare Us -1
TOTALCMD#BAR#DATA cmd /c mklink /J %T%N %P%N %Commander_Path%\wciconex.dll,53 MKLINK JUNCTION -1
/cmd cmd "-new_console:t:%P"
TOTALCMD#BAR#DATA c:\Program Files (x86)\Vim\vim74\gvim.exe --remote-tab-silent "%P\%N" C:\Program Files (x86)\Vim\vim74\gvim.exe VIM -1
TOTALCMD#BAR#DATA c:\Program Files\ConEmu\ConEmu64.exe /cmd e:\Program Files\PyCmd\PyCmd.exe"-new_console:t:%P" -1
TOTALCMD#BAR#DATA c:\Program Files\ConEmu\ConEmu64.exe /cmd E:\CYGWIN_BIN\bin\bash.exe . -1
TOTALCMD#BAR#DATA c:\Program Files\ConEmu\ConEmu64.exe -new_console:t:%P" -1
TOTALCMD#BAR#DATA e:\Program Files\cmder\Cmder.exe /START %P -new_console:t:%P -1
TOTALCMD#BAR#DATA c:\Program Files\Everything\Everything.exe -p "%P" Everything -1
open_folder_command2=$exec("%TOTALCOMMANDERPATH%\totalcmd64.exe" /O /T "%1") open_file_command2=$exec("%TOTALCOMMANDERPATH%\totalcmd64.exe" /O /T /L="%P" "%1") open_path_command2=$exec("%TOTALCOMMANDERPATH%\totalcmd64.exe" /O /T "$parent(%1)")
TOTALCMD#BAR#DATA c:\Program Files\ConEmu\ConEmu64.exe /cmd "cmd.exe /s /k clink_x64.exe inject" "-new_console:t:%P" -1
$ ssh -X user@server “export DISPLAY=:0; gnome-screensaver; gnome-screensaver-command -l;”
You may use that command without “-X” option if you have X forwarding enabled (ForwardX11 yes) on your ssh configuration. But you need to remember with “export DISPLAY=:0”, without this the command will give the lock screen on your computer, not your remote computer.
To unlock the screen on your remote computer, type this command on your computer :
$ ssh -X user@server “export DISPLAY=:0; gnome-screensaver; gnome-screensaver-command -d;”
sumber : http://z-computer-z.blogspot.com/2010/01/remote-lock-screen-and-remote-unlock.html
Jika terjadi keanehan pada komputer remote, semisal sewaktu tekan huruf ‘m’ maka window yang aktif menjadi minimize, jalan keluarnya ada dengan menekan Windows Key + D. Entah kenapa saya juga tidak tahu tapi hal tersebut sangat mengganggu.
sumber : http://marcipsen.wordpress.com/2009/07/20/strange-keyboard-behaviour-using-remotedesktop-on-win7/
select
owner,constraint_name,constraint_type,table_name,r_owner,r_constraint_name
from all_constraints
where constraint_type in (‘P’,’U’)
and table_name=’table_name’;
sumber :
1. http://www.databasejournal.com/features/oracle/article.php/3665591/Finding-Foreign-Key-Constraints-in-Oracle.htm
ssh -X me@mydomain.com
screen
export DISPLAY:0.0
teamviewer
sumber : http://ubuntuforums.org/showthread.php?t=1545451
You can throw user-defined error messages from PL/SQL code. Error codes between -20000 until -20999 are reserved for user specified error messages. You do so by calling the raise_application_error function within your PL/SQL:
raise_application_error(-20001, ‘Your error code message here’);
This will be propagated just like normal Oracle errors.
sumber : http://stackoverflow.com/questions/1544035/throwing-specific-error-messages-in-plsql-oracle-catching-in-hibernate
Have you ever integrated a third party library into your project? You got a big manual full of nice documentation. At the end there was a thin appendix of examples. Which of the two did you read? The examples of course! That’s what the unit tests are! They are the most useful part of the documentation. They are the living examples of how to use the code. They are design documents that are hideously detailed, utterly unambiguous, so formal that they execute, and they cannot get out of sync with the production code.
sumber : http://butunclebob.com/ArticleS.UncleBob.TheThreeRulesOfTdd