Venkat Iyer

I prefer emacs anytime.  Fervent Tcl-Tk disciple.

v e n k s i at y a h o o dot c o m

Sometimes venks in the [Tcl Chatroom]

My Humble Contributions:

   * [Poor Man's Expect]
   * [cwind on avi2vcd]
   * [smake musings]
   * [gidrw]
   * [WMF] is something I'm working on
   * [DBM] and the related [vacprint]
   * [Minimalist Curses] and [curses banners], [curses digital clock]
   * A derivative of smake in [svmk]


----
vi is also a modal based editor.  It's connection to Tcl is that
there are several vi-like editors which provide an embedded Tcl
interpreter, which can be programmed to manipulate the text.  Others
support Tcl syntax highlighting, etc.

Some of these are:

   * [Elvis] supports Tcl syntax highlighting
   * [vile] supports Tcl syntax highlighting
   * [vim] supports Tcl syntax highlighting and supports embedding Tcl in the editor
   * [nvi] supports an embedded Tcl interpreter
   * tcltags generates vi [symbol tags] files, for locating symbols in files being edited.
   * [js tools] includes the jedit test editor, which has some vi-like bindings.

----
[SS]: Are there editors written in Tcl with vi key bindings? [ctext] may provide syntax highlighting.
The point isn't just that the editor is written in Tcl, but the fact that such an editor can be made
scriptable in a much more prevasive way than [vim] can.
I'm a [vim] user, but I must I'm not comfortable with its scripting capabilities.

----
[[
[Category Person]
|
[Category Application]
]]