I should mention, I"m going to try Christian's plug-in. :)
On Jan 19, 6:21 pm, Christian Brabandt 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 that the sp
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 ma
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 that the speed was
> > adjustable, but that would be useful.
[…]
While we are at that part, I started to read into the undo-
Hi Gary!
On Mo, 18 Jan 2010, Gary Bickford wrote:
> In other cases, when one either screwed up on a big change and wanted
> to go back to just before the change, you could replay the transcript
> to just before the big change, step forward and back one change at a
> time, then stop the replay and
On Jan 18, 9:56 am, Gary Bickford wrote:
> Back in the day, on the Perq workstation, the text editor had a very
> handy feature. It retained a transcript file for every change made to
> a file, from the time it was created. The transcript could be
> deleted, and then from then on it would reta
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 transcri
