romainthd/ash

A shell emulator for web browsers using Angular

ash's Issues

[cmd] The commands should either use backquotes or single quotes for files and command names, not both

Example : man uses backquotes, while ls _ uses single quotes

[fs] How to handle duplicate files ?

Throw an exception ? Return null ? Silently overwrite ?

[front] The prompt cursor is misaligned before any input

[cmd] `cat` on a directory is incorrectly reported as a `NotFound`

The problem is the use of File.findFromPath, which will already filter the other inodes

[front] Not all ANSI escape codes are currently supported

For example, \033[4;32m, which should underline (4) AND color in green (32).

The part between [ and m should be treated as a list of consecutive parameters.
For example, \033[4;0;31m should be exploded as \033[4m \033[0m \033[31m

[front] Same ANSI colors following each other are not rendered correctly

For example, "BLUE BLUE foo RESET" will render "BLUE foo" in blue, where BLUE is the ANSI color code.

[cmd] `echo` prints the quotes

echo "abcde" will output "abcde"

[build] `assert` isn't working because of Webpack

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.        
This is no longer the case. Verify if you need this module and configure a polyfill for it.        

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "assert": require.resolve("assert/") }'
        - install 'assert'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "assert": false }

[front] Going back in history will put the cursor at the beginning of the command

The expected behaviour would be to set it to the end of the word

[build] The production build throws an error if minimized

Uncaught ReferenceError: can't access lexical declaration 'qu' before initialization

[front] An empty command propagates `undefined`

[cmd] A `help` command would be helpful

[cmd] An empty command should not do anything

Right now, an empty command might be treated as not recognized

[cmd] The environment path is incorrect

For example, cd .. will write root:12:00:00:..$

[cmd] `mkdir` doesn't respect the current working directory

[cmd] `ls` prints an absolute path when the directory is not found

[cmd] Should the escape sequences be parsed in the command line ?

Should the following commands raise an error ?

cat "./foo\0bar"
touch new\nfile

If so, what about this ?

echo "foo\nbar"

Otherwise, should the command be parsed, and then the JavaScript string be filtered / checked in the command itself ?

[cmd] Escaped spaces are currently not supported

Example : ls my\ directory

[test] `cat` doesn't work correctly in the testsuite

[front] There is a vertical scrollbar even when the CLI is empty