[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: UTP Revisited: scoping the project
From: |
Marc Chantreux |
Subject: |
Re: UTP Revisited: scoping the project |
Date: |
Tue, 20 Oct 2020 21:16:45 +0200 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
> > * improve the chapter to take advantage of modern implementations of
> > vi in modern unix.
>
> Your last point was exactly where I was going with this. Having your editor
> (gvim in this case) in one window, and your shell in another, makes life so
> much easier, for example. Cherry-pick one or two things like that, then
> point out that we’re only scratching the surface of what modern versions
> can do. Point them to vim.org for more info.
looks very good to me: things like as, ap, autowrite, the %
expand or even syntax highlighting are really useful indeed.
i'm very afraid of the new vimers using tons of plugins to do jobs that
are possible with ! command from the very begining of vi.
sorry for disturbing :)
> I’ve not used another editor where you can pipe chunks of text *ad hoc*
> through scripts or even awk/perl one-liners.
except ed, sam (AFAIR), and every vi clones i used.
regards.
- Re: UTP Revisited: scoping the project, (continued)
- Re: UTP Revisited: scoping the project, Ingo Schwarze, 2020/10/20
- Re: UTP Revisited: scoping the project, Larry McVoy, 2020/10/20
- Re: UTP Revisited: scoping the project, Larry Kollar, 2020/10/20
- Re: UTP Revisited: scoping the project,
Marc Chantreux <=
- Re: UTP Revisited: scoping the project, James K. Lowden, 2020/10/22
Re: UTP Revisited: scoping the project, Mike Bianchi, 2020/10/20