Re: "file locked by another user" mystery
- From: Big John <john.powers@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Feb 2008 00:31:47 -0800 (PST)
I don't know where you got the idea that edit will only process a
single file spec, but this is definitely not the case (of course you
mentioned TPU, and it is possible to write your own editor in TPU that
will only process the first filespec in a list, but I assume you are
referring to the default dec-supppied EVE editor)..
$ edit login.com,debug.ini
[From the full screen, hit the DO and type]
Command: show buffers
-and you get the list
Buffer name Lines Attributes
LOGIN.COM 152
DEBUG.INI 4
- It clearly does not ignore all but the first file specification in
the list. Perhaps you are confusing it with EDT, which does not
process file lists. But in this case, it does not pretend to..
ß edit/edt login.com,debug.ini
%DCL-W-NOLIST, list of parameter values not allowed - check use of
comma (,)
\LOGIN.COM,DEBUG\
-Both cases correctly match the documented behaviour. Perhaps you are
getting them confused?
- John
On Feb 8, 5:54 pm, chessmaster1...@xxxxxxxxxxx wrote:
On Jan 31, 10:05 pm, AEF <spamsink2...@xxxxxxxxx> wrote:> On Jan 29, 6:14 pm, Fred Bach <b...@xxxxxxxxx> wrote:
The reason the status for TYPing a non-existant file is only a warning
is simple - it does not abort TYPE. If your TYPE command line has a
list of files and one or more of the files in the list do not exist,
TYPE will output the warnings for those files but continue and type
out any files in the list that do exist. The %TYPE-W-SEARCHFAIL
warning is returned as the final status even if the final file in the
list was ok.
The behaviour is similar if one of the files found can not be opened
by TYPE, for example due to it being locked by another user. You get
a %TYPE-W-OPENIN warning and then TYPE moves on to the next file.
This could happen even if you used a single file specification if it
has wildcards..
Strangely though when both of these warnings occur %TYPE-W-SEARCHFAIL
is always returned as the final status even when %TYPE-W-OPENIN occurs
for the final file accessed.
EDIT, on the other hand, will only process a single file spec (the
default EDIT verb syntax does accept a file list, but as far as I can
tell TPU ignores all but the first file specification in the list).
Since in this case you are only processing one file it makes sense
that any error accessing that file would be a fatal error.
Well, I wouldn't want to STOP on severe errors as I'd probably want to
do some cleanup. Also, it's somewhat arbitrary what constitutes a
warning vs. an error vs. a "severe error". Why should editing ADSF: be
fatal while TYPEing it only a warning?:
$ TYPE ASDF:[ASDF]ASDF
%TYPE-W-SEARCHFAIL, error searching for ASDF:[ASDF]ASDF.LIS;
-RMS-F-DEV, error in device name or inappropriate device type for
operation
$ SH SYM $SEVERITY
$SEVERITY == "0"
$
$ EDIT/EDT ASDF:[ASDF]ASDF
%EDT-F-OPENIN, error opening ASDF:[ASDF]ASDF.; as input
-RMS-F-DEV, error in device name or inappropriate device type for
operation
$ SH SYM $SEVERITY
$SEVERITY == "4"
$- Hide quoted text -
- Show quoted text -
.
- Follow-Ups:
- References:
- Re: "file locked by another user" mystery
- From: AEF
- Re: "file locked by another user" mystery
- From: chessmaster1010
- Re: "file locked by another user" mystery
- Prev by Date: Re: DIBOL to <different language>
- Next by Date: XP1000 and DEGPA-TA
- Previous by thread: Re: "file locked by another user" mystery
- Next by thread: Re: "file locked by another user" mystery
- Index(es):
Relevant Pages
|
