VI for SpartaDOS ?

[w1k]

crash on altirra?

[greblus]

 

I cannot guarantee fixing anything, but if you observe some consistent behaviour, tell me, we will see what can be done.

Here is a version which accepts fname to load in the command line.

 

This version is not crashing when yanking and putting.

Thank you again.

[drac030]

 

This version is not crashing when yanking and putting.

Thank you again.

 

That is not good because I did not change anything in the program I just added some code at the beginning, which parses a CLI argument. Which means that "tad unstable" behaviour you observe may be dependent on the position of the code in the memory. In turn, whether this is something inherited from the original, or my error during sourcing the binary, it for now remains unknown.

 

@w1k: Altirra:

[greblus]

That is not good because I did not change anything in the program I just added some code at the beginning, which parses a CLI argument. Which means that "tad unstable" behaviour you observe may be dependent on the position of the code in the memory. In turn, whether this is something inherited from the original, or my error during sourcing the binary, it for now remains unknown.

 

The original binary was also crashing when yanking and putting, so most likely it's as you say: depending on position in memory.

 

Update: It just crashed, in the romantic way

 

Edited December 24, 2013 by greblus

[danwinslow]

Heh - that's the way to get things done. Unfortunately, I can't test it, since the ZIP appears corrupt.

Hah! I did the same thing Jon. I even posted a ? to drac about it but caught my error adn edited it

 

I suppose we could could disassemble this....

[drac030]

I have it already disassembled. For testing purposes I could prepare a binary which loads at a page boundary or at a fixed address. This perhaps could help to improve the consistency of the program's behaviour and to identify problems using a debugger.

[flashjazzcat]

Hah! I did the same thing Jon. I even posted a ? to drac about it but caught my error adn edited it

Well, in my defence, I read his original post on a 4" mobile phone screen on a bus full of screaming children, and by the time I got home I was paying no heed to the detail... I was just excited to test it.

 

I suppose we could could disassemble this....

I disassembled it using DIS6502 at the weekend, but Konrad's making such an excellent job of it and is so far ahead of me by a country mile, I'm happy to leave him to it.

 

EDIT: (Optional) expanding tabs would be great, BTW, especially in 80 columns.

Edited December 24, 2013 by flashjazzcat

[flashjazzcat]

I have it already disassembled. For testing purposes I could prepare a binary which loads at a page boundary or at a fixed address. This perhaps could help to improve the consistency of the program's behaviour and to identify problems using a debugger.

I wondered while looking at the code if some of it depended on certain parts being page-aligned or some such. This sounds like an excellent idea.

[drac030]

One more version, I have remapped some key combos to match vi documentation: ctrl-g, ctrl-e, ctrl-y, ctrl-f, ctrl-e instead of the same keys with inverse video. Yet some remain to be remapped similarly (I guess the original author thought that the Inverse video key on Atari is an equivalent to Ctrl?).

 

I have also added initializing all variables to zero, just in case it improves anything (I doubt). I have also managed to reproduce the copy/paste problems, this looks like some pointer gets clobbered, and it indeed looks like a bug in the original.

 

Today I will not do anything more with it. Happy Christmas again.

vi65.zip

[w1k]

[flashjazzcat]

Hit Debug. Also describe what you were doing when it crashed.

[w1k]

sure

 

PC = 022F (0230)
A = 38
X = 20
Y = 80
S = F9
P = B0
N-----

CPU: Illegal instruction hit: 0230
( 16:311,111) A=38 X=20 Y=80 S=F9 P=B0 (N ) 022F: 22 SDMCTL bad

Edited December 24, 2013 by w1k

[Frankie]

It works for me on real hardware!

So my next comment is that I'm used to doing write and quit at the same time

 

:wq

 

This version you need to do them separately for some reason.

 

Frank

[drac030]

Let us first wait for w1k to answer fjc's question.

[w1k]

its not a com/xex file

[phaeron]

It looks like w1k is trying to run the program directly from Altirra. That isn't going to work since it needs SpartaDOS.

[+Ripdubski]

Stoked to see this throughi completeion!

[Creature XL]

It is ":e filename". I do not know, why not ":r".

 

E is for edit. At least that is what I use with vi.

Have you tried :e . ?

Should list the directory for loading files.

 

[danwinslow]

:r is for read, as in 'insert the file into the current buffer at the cursor location'

[576XE]

phaeron absolutely right.

VI.ZIP is really VI.COM - SDX executable file.

[tschak909]

FWIW, if I need a quick edit, I use vi.

 

If I need to do coding, I typically use emacs. The facilities for C/C++ coding in emacs are just enough, and quite intelligent, without stepping on your toes like many other editors (Eclipse, I am talking to you, you over-bloated piece of shit!)

 

-Thom

[+Ripdubski]

FWIW, if I need a quick edit, I use vi.

 

If I need to do coding, I typically use emacs. The facilities for C/C++ coding in emacs are just enough, and quite intelligent, without stepping on your toes like many other editors (Eclipse, I am talking to you, you over-bloated piece of shit!)

 

-Thom

Can not stand Eclipse. . . . . . . .

[Steve Mynott]

Were the SD fixes ever applied to the 80 col version of vi65? Would it work with s_vbxe?

 

Note the vi65 sources are at

 

https://sourceforge.net/p/vi65/code/HEAD/tree/branches/v0.2/

 

svn checkout svn://svn.code.sf.net/p/vi65/code/ vi65-code

 

I was sort of hoping for CC65 but it's ASM