Linux Today: Linux News On Internet Time.
Search Linux Today
search.internet.com
Linux News Sections:  Blog -  Developer -  High Performance -  Infrastructure -  IT Management -  Security -  Storage -
Linux Today Navigation
LT Home
Preferences
Contribute
Link to Us
Search
Linux Jobs

Become a Marketplace Partner

internet.commerce
Be a Commerce Partner














The Linux Channel at internet.com
Linux Today
Enterprise Linux Today
Apache Today
JustLinux.com
Linux Planet
PHPBuilder
All Linux Devices
Technology Jobs

JustTechJobs.com

LinuxToday Newsletters
Server Daily
IT Management Daily
Subscribe News
Subscribe PR
Subscribe Security

internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

 






Current Newswire:

Slashdot Struggles to Remain Relevant in The Social Web

Python development - the golden rules

Digital Copywrongs

ATM hack gives cash on demand

Systems Administrators Changing Roles

Toshiba NB300 netbook review

Create an Application Shortcut to Open Nautilus as Root in Ubuntu

Basket – A Multi-Purpose Note Pad For KDE

Demonstrating multi-processing in Bash 4

Spotlight on Linux: SimplyMEPIS 8.5.x




Implementation Engineer Sr – Windows (TX)
Next Step Systems
US-TX-Houston

Justtechjobs.com Post A Job | Post A Resume
:Scripting the Vim editor, Part 5: Event-driven scripting and automation
Scripting the Vim editor, Part 5: Event-driven scripting and automation
Mar 10, 2010, 23 :32 UTC (0 Talkback[s]) (2643 reads)

(Other stories by Damian Conway)

"Vim’s event model

"Vim’s editing functions behave as if they are event-driven. For performance reasons, the actual implementation is more complex than that, with much of the event handling optimized away or handled several layers below the event loop itself, but you can still think of the editor as a simple while loop responding to a series of editing events.

"Whenever you start a Vim session, open a file, edit a buffer, change your editing mode, switch windows, or interact with the surrounding filesystem, you are effectively queuing an event that Vim immediately receives and handles.

"For example, if you start Vim, edit a file named demo.txt, swap into Insert mode, type in some text, save the file, and then exit, your Vim session receives a series of events like what is shown in Listing 1."

Complete Story

Related Stories:
Scripting the Vim editor, Part 4: Dictionaries(Feb 17, 2010)
Scripting the Vim editor, Part 3: Built-in lists(Feb 02, 2010)
Vim Tip: using "paste" to avoid the staircase effect(Dec 27, 2009)
Vim 201: An Intermediate Guide to Vim(Nov 27, 2009)
Vim 101: A Beginner's Guide to Vim(Nov 21, 2009)



No talkbacks posted.
  Home | Search Talkbacks | Customize View    Top of Page  



Enter your comments below:

* Your Name:

* Your Email Address:

* Subject:

CC: [will also send this talkback to an E-Mail address]

* Comments:

Tags allowed:<I>,<B> and <U>. See our talkback-policy for more about talkback content.

Fields marked with * are required!






..............................




All times are recorded in UTC.
Linux is a trademark of Linus Torvalds.
Powered by Linux, Apache and PHP