Skip to content
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

vi cannot be opened the second time #123

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 9 comments
Closed

vi cannot be opened the second time #123

GoogleCodeExporter opened this issue Mar 14, 2015 · 9 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. open vi, add "forget bg"
2. :q to quit editor
3. try to open again typing 'vi'

What is the expected output? What do you see instead?

The editor should open, but I just see "err", like if "vi" is not recognized 
anymore.

Please provide any additional information below.

I'm accessing the D64 on my uIEC/SD device, on a C128 in C64 mode. The first 
time everything seems normal, but as soon as I quit vi, it won't open anymore. 
"ls" still works though.



Original issue reported on code.google.com by pedgar...@gmail.com on 30 Mar 2014 at 3:30

@GoogleCodeExporter
Copy link
Author

Cannot reproduce :/  What version are you using?

Original comment by kotlin...@gmail.com on 30 Mar 2014 at 7:58

@GoogleCodeExporter
Copy link
Author

I'm using the 1.26. 

I'm basically following the first steps on your guide, with the bg command. 

Everything works as you wrote, until the point I enter the flash example and 
try to compile with F7 in vi.

At this point, the prompt returns with a reversed ":?" and I can't do anything 
else. 'vi' , 'ls' is all not recognized anymore.

It seems the interpreter can't understand the : at the beginning of my program.

As you can see, I'm new with the tool, so I might be doing something wrong here.


Thanks

Paulo

Original comment by pedgar...@gmail.com on 30 Mar 2014 at 2:50

@GoogleCodeExporter
Copy link
Author

Oh, I see now. That was an error in "forget" word. Please download new version, 
1.27. Sorry & thanks a lot for reporting :)

Original comment by kotlin...@gmail.com on 30 Mar 2014 at 4:00

@GoogleCodeExporter
Copy link
Author

Original comment by kotlin...@gmail.com on 30 Mar 2014 at 4:01

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Thanks, I've tried this new version and I could move forward. One thing that I 
noticed is that if I keep going back and "forth" :) between the interpreter and 
the editor, the system will crash after few times.

Also, maybe I'm not doing it right, but if I load the turtle into VI, and run 
F7 from there, the system will crash 100% of the times. This was tested in an 
actual C64 hardware using the ueic/SD. I wonder if the fastload could bring 
some instability using the SD card.

I can open a new ticket if that is the case.

Thanks again

Paulo 

Original comment by pedgar...@gmail.com on 30 Mar 2014 at 9:30

@GoogleCodeExporter
Copy link
Author

Hallo! The "turtle" crash is probably because error in turtle.fs. s" gfx" load 
at top should be removed, gfx is now already loaded from start. Loading gfx 
twice will make the system run out of memory. Sorry about that...

About crashing when going back and forth between interpreter and editor. I 
could not reproduce that. Can you describe further? Or make a movie of it, or 
something.
Thanks

Original comment by kotlin...@gmail.com on 31 Mar 2014 at 6:00

@GoogleCodeExporter
Copy link
Author

By the way. I do not think the UEIC should cause any problems.

Original comment by kotlin...@gmail.com on 31 Mar 2014 at 4:29

@GoogleCodeExporter
Copy link
Author

Hmmm... I noticed now that I can't do s" gfxdemo" load when Vice is in IEC 
mode. so Yeah... maybe there is some problem with that after all.

Original comment by kotlin...@gmail.com on 31 Mar 2014 at 5:30

@GoogleCodeExporter
Copy link
Author

Nice, that explains a bit. I will try to play on my real machine using a real 
1571 instead and see how it goes :)

Original comment by pedgar...@gmail.com on 31 Mar 2014 at 6:49

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant