HP3000-L Archives

September 2005, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
john pitman <[log in to unmask]>
Reply To:
john pitman <[log in to unmask]>
Date:
Mon, 5 Sep 2005 11:51:36 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (130 lines)
 

 

 

 

Craig,

Well, once you have learnt the ins and outs (mostly, knowing which mode you
are in at a point in time - command or data) of vi, it is a very effective
editor. I find the '/ to find , change, esc, find next . to do same change
again' scenario much quicker than going to replace in MS visual c++, and for
contextual changes , easier and more controllable than qedit. I looks awful
trying to learn it, when you really cant follow somebody else's keystrokes
by watching them..it gets just too fast to catch. I find change word , or
multiple words very easy to use and also upshift/downshift a word/words
easier than anything else I know.

 

I have also seen the "out of space"  msg from vi on mpe, but I havent seen
it corrupt a file like this before.

 

jp

 

John,

 

First, I have to say, why would you want to do this... but anyway.

 

I thought I would give it a go.


When I did the 

 

:wq

 

I get 

 

"Write error (out of space?)" System call error 

Even though it gave me the error, it kept the change.

Also when I did a :w newfile, this is what I get...

ACCOUNT= TELESUP GROUP= PATCHXL 

FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----

SIZE TYP EOF LIMIT R/B SECTORS #X MX

NPCONFIG 72B FA 115 115 32 48 1 1

 

:listf newfile,2

ACCOUNT= TELESUP GROUP= PATCHXL 

FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----

SIZE TYP EOF LIMIT R/B SECTORS #X MX

NEWFILE 1B BA 2512 2147483647 1 16 1 *

I assure you I have about 12GB available on this one drive and about 30 for
the volume set.

 

vi would not let me save the file as NPCONFIG.

 

 

I am on MPE/iX 7.0, fully patched.

 

-Craig

 



john pitman <[log in to unmask]> wrote:

We had a strange one (to us) recently.

Used vi in sh to edit npconfig.pub.sys, and on trying to do a startspool on
a newly defined printer, got 'Bad variable block structure' error, and the
file was unusable. In fact, it was so unusable that mpe would not purge it
at all, and we had to use fscheck to get rid of it so we could replace with
the backup copy...



Anybody else seen this please....



jp

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2