Topic: A possibly misleading error message. (1 of 7), Read 59 times
Conf: Error messages, Crashes
From: Peter Rejto
Date: Thursday, July 21, 2005 02:11 AM

Hello,

Suppose that in Command mode I enter

Call_File(100, "|(USER_MACRO)\xxx.vdm)

where, xxx.vdm does not exist.

I got the error message,

Can not find "|(HOME)\xxx.vdm.


I would have expected the message,
Can not find "(USER_MACRO)\xxx.vdm.

Of course this is a strictly cosmetic question. I just
thought there is no harm asking it.

Thanks,

-peter.

 


Topic: A possibly misleading error message. (2 of 7), Read 61 times
Conf: Error messages, Crashes
From: Fritz Heberlein
Date: Thursday, July 21, 2005 08:45 AM

>I got the error message,
>
>Can not find "|(HOME)\xxx.vdm.
>

I get "file not found c:\vedit\xxx.vdm"

This seems to be the logical outcome of Vedit's search procedure: first user-mac\, second second macros\ and home\.

So, there seems to be nothing wrong with that message.

Fritz

 


Topic: A possibly misleading error message. (4 of 7), Read 61 times
Conf: Error messages, Crashes
From: Christian Ziemski
Date: Thursday, July 21, 2005 08:56 AM

Fritz:

It looks like we wrote almost the same in almost the same minutes.. ;-)

Christian

 


Topic: A possibly misleading error message. (3 of 7), Read 57 times
Conf: Error messages, Crashes
From: Christian Ziemski
Date: Thursday, July 21, 2005 08:53 AM

On 7/21/2005 2:11:30 AM, Peter Rejto wrote:

>Call_File(100, "|(USER_MACRO)\xxx.vdm)
>where, xxx.vdm does not exist.
>
>I got the error message
>Can not find "|(HOME)\xxx.vdm.
>[ but expected: |(USER_MACRO)\xxx.vdm ]

Do you really get that exact string with '|(HOME)'?

I'm getting the message:
FILE NOT FOUND: C:\vedit\xxx.vdm

(HOME is c:\vedit on my PC)


That message may not be perfectly clear, but I assume that it's this way due to Call_File()'s behavior:

Quoted from the Online Help:

[ Call_File(r,"file") Load the command macro in 'file' into T-Reg 'r' and execute it.

[ If 'file' is not found in current directory, VEDIT will look for it first in the User Macro Directory,
[ then in the VEDIT Macro Directory, and last in the VEDIT Home Directory.


So the Home directory is last one tested and failing too. And this is reported in the error message.

Christian

 


Topic: Re: A possibly misleading error message. (5 of 7), Read 58 times
Conf: Error messages, Crashes
From: Ted Green
Date: Thursday, July 21, 2005 10:03 AM

At 08:53 AM 7/21/2005, you wrote:
>Do you really get that exact string with '|(HOME)'?

I don't think Peter reported the error message correctly.

>I'm getting the message:
> FILE NOT FOUND: C:\vedit\xxx.vdm

That sounds right.

>So the Home directory is last one tested and failing too. And this is reported in the error message.

And that is exactly correct.

Ted.


Ted.
-------------------------------------------------------------------------
Ted Green (ted@...) Greenview Data, Inc.
Web: www.... Fax: 734-996-1308 PO Box 1586, Ann Arbor, MI 48106
Tel: (734) 996-1300 Desk: 734-369-3550 VEDIT - Text/Data/Binary Editor
-------------------------------------------------------------------------
www.SpamStopsHere.com ranked #1 in accuracy by Network Computing Magazine

 


Topic: Re: A possibly misleading error message. (6 of 7), Read 52 times
Conf: Error messages, Crashes
From: Peter Rejto
Date: Thursday, July 21, 2005 06:34 PM

Thanks gentlemen:

Now I see that from the Vedit point of view this message is perfectly logical. I also see that this message implies that there is no file xxx.vdm in my USER_MACRO directory.
In other words, I can ask Vedit to verify my conjecture.

Incidentally, I quoted the error message from memory. You are
right concerning the exact quotation.

Thanks again,

-peter.

 


Topic: Re: A possibly misleading error message. (7 of 7), Read 51 times
Conf: Error messages, Crashes
From: Pauli Lindgren
Date: Monday, August 08, 2005 06:34 AM

On 7/21/2005 10:03:39 AM, Ted Green wrote:
>
>>So the Home directory is last one tested and failing too.
>>And this is reported in the error message.
>
>And that is exactly correct.

Then maybe it would be better to give just the filename
without path in the error message.

--
Pauli