1 (edited by csanchez71 2013-07-28 17:01:14)

Topic: Make all commands be avaliable as .command

When using esxdos, is quite confusing to have to use a mix between .commands and old commands (like CAT). While browsing a disk there are countless times I make the mistake of writing ".cat"

Even when they may be mere redirectors, rather than a full "cat" implementation, it would be nice to have CAT and any other "standar spectrum" commands avaliable at /BIN as dot commands (.load, .merge, .save, .goto, .erase, .cat).

2

Re: Make all commands be avaliable as .command

Hi,

It is not possible at the moment to have these redirectors, but I will look into this in the future.

3

Re: Make all commands be avaliable as .command

Nice, thanks!

4 (edited by velesoft 2013-07-29 21:38:00)

Re: Make all commands be avaliable as .command

csanchez71 wrote:

When using esxdos, is quite confusing to have to use a mix between .commands and old commands (like CAT). While browsing a disk there are countless times I make the mistake of writing ".cat"

You can duplicate "LS" file in BIN directory but as new filename use "CAT". Now will .CAT in esxdos work identically with .LS command :-)

For faster work and your better comfort you can duplicate + rename also other command in BIN direcotry. For example I use ".I" instead ".TAPEIN", ".O" instead ".TAPEOUT", ".S" instead ".SNAPLOAD", etc...

5

Re: Make all commands be avaliable as .command

velesoft wrote:
csanchez71 wrote:

When using esxdos, is quite confusing to have to use a mix between .commands and old commands (like CAT). While browsing a disk there are countless times I make the mistake of writing ".cat"

You can duplicate "LS" file in BIN directory but as new filename use "CAT". Now will .CAT in esxdos work identically with .LS command :-)

For faster work and your better comfort you can duplicate + rename also other command in BIN direcotry. For example I use ".I" instead ".TAPEIN", ".O" instead ".TAPEOUT", ".S" instead ".SNAPLOAD", etc...

Yes, I had already copied LS into CAT, but it is not a general solution, cause other commands like ERASE don't have a matching dot command.

About the trick of renaming/copying, it's a good idea, in fact I will probably rename or copy some commands.

By the way, is there any documentation about how to make a dot command. I've tried to disassemble one but as I'm not sure if there is a header (for the "executable") I'm not sure what I got did have any sense. Also I tried to create a simple assembler code (just a RET) wih pasmo assembler, and save it in different formats (as binary, as .tap, as binary with +3DOS header..) and then add it to bin folder, but none worked.

Is there any docs?

6

Re: Make all commands be avaliable as .command

There are docs available on request, but the API is undergoing some changes as we speak, so anything you code now will have to be recompiled in a couple of months (when the API will be final and published). Send me an e-mail if still interested.

7

Re: Make all commands be avaliable as .command

I agree, it would be nice to have a .rm command for ERASE.