Tip for VIM

For splitting window.


   : split ( for horizontal split )


   : vsplit ( for vertical split )


Switch between splitted window


   Ctrl-ww


Resize splitted window


   Ctrl-w + / -   ( 1 unit each time, height )


   10 Ctrl-w +   ( resize 10 unit height )


   Ctrl-w < / >   ( 1 unit each time, width )


Search and replace


   :%s/original/replace/g   ( every occur in file )


   :1,$s/original/replace/


   :s/original/replace/g ( replace all in current line )


For multiple files


   :e ( edit file in new buffer )
   :bn ( switch to next file in buffer )
   :bp ( switch to previous file in buffer )
   :bd ( delete file in buffer , ake close file )


   :sp ( edit file in new window )


ETC
   :sh ( switch to console ) and Ctrl-d to get back
   other way
   Ctrl-z (switch to console ) and $fg to get back


   show path of current editing file
   Ctrl-g ( display file's location )
   Ctrl 1 g (display full file's location )

Comments

Post a Comment

Popular posts from this blog

Return Code 127

Exit codes and kill-job signals The exit code from a batch job is a standard Unix termination status, the same sort of number you get in a shell script from checking the " $? " variable after executing a command. Typically, exit code 0 (zero) means successful completion. Codes 1-127 are typically generated by your job itself calling  exit()  with a non-zero value to terminate itself and indicate an error. In BaBar we don't make very much use of this. The most common such value you might see is 64, which is the value used by Framework to say that its event loop is being stopped before all the requested data have been read, typically because time ran out. In recent BaBar releases you might also see 125, which we use as a code for a generic "severe error"; the job log should contain a message stating what the error was. Exit codes in the range 129-255 represent jobs terminated by Unix " signals ". Each type of signal has a number, and what's r
Read more