Mapping Keys to vim to execute commands and scripts

Vim is powerful and light weight source code editor.

vim initialization settings can be done in .vimrc file.

For example if you add  the following vim commands to the .vimrc file.
vim will initialize with the following settings:

.
.
se nu
se hlsearch
se incsearch
se cindent
.
.
.

One power full feature of .vimrc that i know is mapping of  keys to execute the commands
mentioned in .vimrc file.

Below is the .vimrc file  which  executes eco_script_genertor.pl script and does multiple operations.

map Do./eco_script_generator.pl "pa"k0i#pj0D:w:!rm -r -f ./cmd.do:e ./cmd.dop:w:e#:!rm -r -f ./.cmd_out:!source ./cmd.do > ./.cmd_out:r ./.cmd_out

Here Ctrl+M key is mapped to execute the script.

Comments

Post a Comment

Popular posts from this blog

Getting backtrace during stack corruption

As we know , if program crashes and if it results in stack corruption, GDB will never give backtrace of the crashes.Even coredump does not help. Consider the below situation of stack corruption, Is it possible to make out anything useful from this for debugging?No Program received signal SIGSEGV , Segmentation fault . 0x00000002 in ?? () ( gdb ) bt #0 0x00000002 in ?? () #1 0x00000001 in ?? () #2 0xbffff284 in ?? () Backtrace stopped : previous frame inner to this frame ( corrupt stack ?) ( gdb ) Those bogus adresses (0x00000002 and the like) are actually PC values, not SP values. Now, when you get this kind of SEGV, with a bogus (very small) PC address, 99% of the time it's due to calling through a bogus function pointer. Note that virtual calls in C++ are implemented via function pointers, so any problem with a virtual call can manifest in the same way. An indirect call instruction just pushes the PC after the call onto the stack and then sets the PC
Read more

Analyzing Crash dumps in Linux using GDB

GDB is a common tool for debugging applications in Linux development environment. Before generating the core dump use -g compiler option for compiling the application for enabling debugging symbols. 1. set ulimit -c unlimited  in cmd to enable core dump. 2. Then run the application, after application crashes it generates code dump with core.pid file name. 3. Load the application in gdb ex: gdb <path to application> 4. In this step load the core dump by using core-file <path to core dump> command 5.Just use bt for getting the backtrace of the crash which will give you exact location where app has crashed. Use GDB instead of logging which will save your time for debugging !!!!
Read more

.b4s playlist parser WINAMP XML PlaylistFormat

More info on this file format is at http://filext.com/file-extension/B4S This can be parsed using following xml based parser application. /* .b4s parser Application */ /*Author:chandrashekar bs*/ /*email:buggs.cancerion@gmail.com/chandragoan@gmail.com*/ /* I have not added <> for including files because of in google blogs since <> are interprested as htnl syntaxes and content within thos are not appeared*/ #include iostream #include string.h #include libxml/parser.h #include libxml/xinclude.h #include libxml/tree.h #include libxml/xmlIO.h int main(int argc, char **argv) {     xmlDocPtr doc;     xmlNodePtr nodePtr;     xmlNodePtr rootnodePtr;     xmlChar *xmlbuff;     int loopcount1, loopcount2, loopcount3, loopcount4;         loopcount1=loopcount2=loopcount3=loopcount4=0;     if(argc !=2)     {         printf("Usage %s: Enter valid b4s playlist file",argv[1]);     }     char *filename = (char *)argv[1];     doc = xmlParseFile((c
Read more