Subject: | |
From: | |
Reply To: | |
Date: | Wed, 23 Feb 2000 23:04:05 -0500 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Richard Gambrell wrote:
> What I wanted to point out is that this is the kind of picking nits
> that makes great products great, prevents memory leaks, system
> crashes, and generally makes the world a better place...
>
> By the way, has *anybody* supported Wirt's position on the issue?
If Wirt has our private correspondence archived, I pointed out the paste
with implicit <cr> a long time ago. I use QCTerm for things other than
the HP. But even in the HP3K sense, we have some semblance
of this feature with the new :REDO functions of '>' (go to end of line)
and then do something. Most of the cut/paste *without* the <cr> are for
similar things. We are entering repetitive data varying only in the
suffix.
As a router person, cut/paste is invaluable *without* the <cr> for
setting up things like access lists for things you wish to allow. These
have repeated instances of:
access-list 111 permit tcp 192.168.1.1 0.0.0.63 any eq telnet
access-list 111 permit tcp 192.168.1.1 0.0.0.64 any eq smtp
(etc)
Allowing certain machines access outside (or inside depending on where
the access list is applied) to various services. I like to 'copy' the
prefix that is common, and finish out the line manually with the service
I wish to allow.
HP3K examples abound as well, I'm sure, I just can't think of a really
clever one at the moment :-(
Jeff Kell <[log in to unmask]>
|
|
|