yoda54:

I see. You may want to check out a few things on CPAN, then. I just took a brief look and found:

• Proc::InvokeEditor: This module provides the ability to supply some text to an external text editor, have it edited by the user, and retrieve the results.
• AnyEvent::EditText: This little module will start a text editor in a seperate process without stopping the current process. Usually something like a terminal with a vim instance running in it will be started, but also a graphical editor could be used (like gedit or gvim).
• Term::CallEditor: This module calls an external editor with an optional text message via the solicit() function, then returns any data from this editor as a file handle. By default, the EDITOR environment variable will be used, otherwise vi.
• Term::EditorEdit: Term::EditorEdit is a tool for prompting the user to edit a piece of text via $VISUAL or $EDITOR and return the result
• Term::ReadLine::Zoid:This package provides a set of modules that form an interactive input buffer written in plain perl with minimal dependencies. It features almost all key-bindings described in the posix spec for the sh(1) utility with some extensions like multiline editing; this includes a vi-command mode with a save-buffer (for copy-pasting) and an undo-stack.

Some of those look interesting. (There were a few pages of stuff that didn't look interesting, though...)

...roboticus