TSE: Error: Can not load file

[knud van eeden]

Hello,

TSE Linux 4.50.13 clean:

When compiling .s files (escape > macro > compile) I get now suddenly

'Can not load file <filename>.'

It seems to add a dot '.' at the end of the file.

with friendly greetings

Knud van Eeden

[knud van eeden]

Can not be reproduced anymore.

Can be closed.

--

---
You received this message because you are subscribed to the Google Groups "SemWare TSE Pro text editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to semware+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/semware/479561172.862805.1759944848741%40mail.yahoo.com.

[knud van eeden]

No, still there. Seems to be an issue.

[S.E. Mitchell]

I cannot reproduce.

I need complete details:

Is the macro in the same directory as the editor, or a different directory?

Can you reproduce it with foo.s ?

What is the setting of SeachCurrentDirectory?

Thank you.

To view this discussion visit https://groups.google.com/d/msgid/semware/323273636.883907.1759947244061%40mail.yahoo.com.

[knud van eeden]

I have seen it a couple of times, also after fresh installation.

At the moment I assume it is caused by the 

(xterm) editor window (e.g. a specific size) for some reason.

Not sure how I can reproduce it as it then suddenly it works again.

If I can reproduce it I will come back.

For now it again can be closed.

To view this discussion visit https://groups.google.com/d/msgid/semware/CA%2BgEvkbZvRYSkwMGDwptUkHXM5ukDtr4NkE%3DSrapQS0zhMs2mA%40mail.gmail.com.

[knud van eeden]

So the case can be closed.

It is a local issue here, caused by some TSE macro loaded.

It can not be reproduced by a clean TSE Linux 4.50.13.

It is seen e.g. as a result of syntax errors involving a filename 

Running this program:

PROC Main()

 STRING fileNameS[255] = "/mnt/c/temp/tse_linux/ddd.txt" )

END

with root cause the spurious ')' at the end of the line,

Then I see in my Linux WSL: TSE Linux 4.50.13 (with some extra TSE macros loaded

at startup)

But in a really clean TSE Linux 4.50.13 it shows correctly:

In Microsoft Windows: TSE 4.50.13: clean installation: it shows the same error message:

[knud van eeden]

At the moment the most likely root cause is having a non-existing TSEPath directory

(it shows the path in Linux WSL notation).

This is set in my startup TSE macro (but running this on Linux non-WSL thus,

with the wrong non-existing path):

 -e <mystartupmacro>

So when compiling the compiler sc32 looks into certain

directories including TSEpath which it can not find thus.

==

Screenshot of a working directory as a Linux WSL path, 

but running it in Linux non-WSL.

So the issue starting to become visible after compiling.

I will change the directories accordingly and if I do not come back it

is resolved with that action.

[knud van eeden]

That is now very likely finally resolved.

Very hard to troubleshoot, with very many

re-installations of a clean TSE.

What happened was that I have my own 

 compile.s

TSE macro in my working directory, e.g. "foobar".

It is intended and only used until now for TSE on Microsoft Windows

and run instead of the native TSE compile.s located in the 

TSE mac directory.

Now on Linux in my startup program '-e mystartupmacro' I made a 

change to that working directory where my compile.s was located.

 ChDir( "foobar" )

So that activated using that own compile.s instead,

that for some reason also without errors

automatically was compiled on the Linux system

using earlier 

 ./sc32 *.s

So then when compiling instead of using the TSE native

compile.s it used my own compile.s located in that "foobar" directory.

And when compiling inside the TSE editor it gave all kind of 'File not found' errors and 'Path not found' errors

and did not compile while in the TSE editor anymore or ignored obvious syntax errors

(but on the command line using sc32 it did compile).

And it persisted even after TSE restarts, so had to reinstall a clean TSE

again.

Finally after about eliminating all possible root causes down

to 'ChDir( "foobar" ) and seeing it only when involving that particular "foobar" directory

and not with another e.g. clean directory, then when looking for purging macros in the TSE menu I saw a 'COMPILE' macro in the list

of macros. That was suspicious because compile should be native to TSE. 

So realized it must be that own compile.s interfering and running.