irmen / cx16shell Goto Github PK

This also happens if you scroll to a different line, where it will continue to happen until the cursor reaches the bottom of the screen

Those of us who grew up in the Wintel world are used to typing "DIR" to get a directory listing. I have 30 years of muscle memory to overcome, and even on Linux, I've noticed that many distros now alias dir to ls, sometimes even changing the format to be more DOS-like (-aL is my favorite.)

Adding "dir" would make things much easier for DOS users. This can be functionally equivalent to "ls"; just another spelling for the same command.

When using cx16-shell as AUTOBOOT.X16 I'm running into an issue where VooV doesn't seem to want to run. It does run if I don't boot into the shell however so I know the program works. Here's all the things I did in the shell:

cd games
cd vindicator
vault

Trying vault,VAULT, VAULT.PRG, and vault.prg all seem to do the same thing - it tries to load, shows something on the screen very briefly (I can't see what it is) then drops back to shell. It's a warm shell though - system didn't fully restart since I'm in the same directory (so running ls shows me the files I expect to see in the 'vindicator' directory.

Recently a couple of changes were made to the shell to prepare for user-customizing it.
In #9 a bunch of questions were raised concerning a way to have a startup and/or config file for the shell.

Let's discuss this topic here.

1. are we going to continue using modt.txt for now, or we'll implement shell.rc from the beginning?

motd.txt shall remain purely a text file.

We shall have a second file that will contain the commands to run at startup. Call it shell.rc or init.sh or something like that. I guess the rc one is closer to the name of similar files used by other shells (bashrc and such)

2. are we going to work from my current commits or should we start form scratch again?

I'm guessing start over? There wasn't much here atm and it was going the route of modifying motd.txt, what I don't like.

3. if we implement shell.rc, should we make a separate folder for config files maybe, or are we going to place everything into SHELL-CMDS as it is now? (i think we will need to make subfolders of SHELL-CMDS sooner or later - I already had an idea of a lib folder while back ago for hypothetical more complex command-line software, that'd need external libraries)

I don't know about this. I don't see a benefit yet to make more subdirectories. There's not much in shell-cmds right now so it's not cluttered at all as it is

4. are we going to allow everything or maybe only selected commands for safety (I guess the answer's everything, based on what you said)
5. If we go shell.rc route, should it be just for executing commands on boot or should it also be a config file? If so, how are we going to differentiate between a config option and a command?

Yeah I think we should keep it simple, just interpret every line as a command to execute (+ its arguments). A while ago I added a few configuration commands to the shell to set the screen mode and colors, so those can be in the file just as well.
The last command in the file could be cat //shell-cmds/:motd.txt to get the shell to write the motd text file if you so desire. So no more special logic in the shell itself is needed to print this file.

I guess we need a way to add a comment line as well. Maybe if it starts with '#' . Or implement a 'rem' command (naaah).

6. If shell.rc route, what if user doesn't have the shell.rc? Will SHELL.PRG create a default config, crash, or run some kind of default routine completely ambiguous to end user?

Just start the shell as it starts now? It's not a failure condition to have no config file. It could create a new (empty?) one if none exists (with a comment in it to tell its purpose?) but that's a nice to have

7. Multiple commands in shell.rc? (probably yes)
8. is Motd on boot going to be configured in shell.rc or will it run regardless of what shell.rc says?

I think these have been addressed above!

I'm having a problem with the "cp" command.

Even though the files are absolutely there the syntax:
cp oldfile newfile
Always gives me an error:
31, SYNTAX ERROR, 00, 00

I've tried with the version that came on the SD card and also I've compiled v1.2.

My ROM version is R47 pre-release.

The ux for this editor is a workalike to nano as the kids know it (clone of pico); in any case it's a small nit but also a surprise when I opened it up and it was basically nano. I'll surely take it, but it's going to be confusing to a lot of people drawn to this shell. Overall, this shell is awesome. TY.

Both 0x123 and 0b01010 get read as 0