-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nested included
broken?
#558
Comments
Hrmm. Went back to durexForth v4 and it still was bugged. I recently reconfigured VICE to use a host file system device. I changed it back to True Drive Emulation and put these two files on a disk image and it worked correctly. Possibly a VICE bug? Weird that I hadn't run into it before, I've been using host drive device for a week now. |
VICE's host filesystem device is super convenient, but also behaves a bit bizarrely. Any time I try to load a file in |
I wonder if the JiffyDOS ROM could also be related? |
I don’t know, but I had problems recently that only disappeared when I
disabled ”handle true drive emulation at autostart”, if i remember
correctly.
ons 17 maj 2023 kl. 05:02 skrev ekipan ***@***.***>:
… I wonder if the JiffyDOS ROM could also be related?
—
Reply to this email directly, view it on GitHub
<#558 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAY34OZEXYUQGWAOT7V6FLTXGQ5WHANCNFSM6AAAAAAYEMAAS4>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Using the latest build. Files test1 and test2:
.( test2 )
Interpreter session (brackets mean inverted text):
durexForth parse-name test1 included test1 test2 [up?]
The text was updated successfully, but these errors were encountered: