Bram Moolenaar wrote:
Gary Bickford wrote:
I often misuse vim to view log files while debugging batch jobs. It is
very handy for moving around in the file, viewing the colorized content
and searching for relevant text. These log files can be from several
thousand to millions of lines
I often misuse vim to view log files while debugging batch jobs. It is
very handy for moving around in the file, viewing the colorized content
and searching for relevant text. These log files can be from several
thousand to millions of lines. Vim does a remarkably good job of
handling these
Another possible suggestion - use the docuwiki format, and save the
file as .wiki. It's a simple format to use, and can be easily pushed
onto the web using docuwiki. AFAI can tell the VIM wiki plugin
doesn't have folding support however.
--
You received this message from the vim_use maillist.
There are some good ideas here, I'll check them out. I wonder though
- the recovery file exists already (if the vim session has gone
away). Does it contain the change history, or just the final state?
If it contains the change history, then it seems that there might be a
way to use that in the
I should mention, Im going to try Christian's plug-in. :)
On Jan 19, 6:21 pm, Christian Brabandt cbli...@256bit.org wrote:
On Mo, 18 Jan 2010, Christian Brabandt wrote:
The amusing part was that you could watch as the editor replayed your
actions at an accelerated speed. I don't recall
Has anyone built a session transcript plug-in for vim? I am aware of
the macro capability, and the kill-ring plug in, and some other
suggestions but I haven't seen anything quite like this:
Back in the day, on the Perq workstation, the text editor had a very
handy feature. It retained a
