1. npm install cash-global -g
2. Restart pc
3. 'ls' is not recognized as an internal or external command, operable program or batch file

However when I do cash it works as before. Am I missing something?

C:\Users\stani>node -v
v5.9.1
C:\Users\stani>npm -v
3.8.3

This adds source as requested in the roadmap.

This executes any given cash script in the current environment, allowing it to modify variables, aliases, current directory, etc.

I also added in code to check for an initialization file, as requested in #20. This file is named .cashrc on Linux/unix systems (following the common convention), and is named _cashrc for Windows (this is consistent with how vim looks for _vimrc, _gvimrc, etc. This file must be located in the user's home folder.

I tried allowing this to be an external command, so deps and such should be double checked for that.

Just tried this after #60 got merged. The output still doesn't seem quite right. Here's the output I'm seeing from cash:

bash $ ./bin/cash.js
nate@lenovoyoga:~/programming/cash$ ls README.md bin/
README.mdalias.js    cash.js     cat.js      cd.js       clear.js
cp.js       echo.js     export.js   false.js    grep.js
head.js     kill.js     less.js     ls.js       mkdir.js
mv.js       parser.js   pwd.js      rm.js       sort.js
source.js   tail.js     touch.js    true.js     unalias.js
nate@lenovoyoga:~/programming/cash$ exit
bash $ ls README.md bin/
README.md

bin/:
alias.js  cp.js      head.js   mv.js      source.js
cash.js   echo.js    kill.js   parser.js  tail.js
cat.js    export.js  less.js   pwd.js     touch.js
cd.js     false.js   ls.js     rm.js      true.js
clear.js  grep.js    mkdir.js  sort.js    unalias.js

If multiple arguments are passed, directories should be displayed with the directory name above, followed by a colon (ex. bin/:). I couldn't find this issue if only directory arguments are used, only when both file and directory arguments are used.

Just tried this out with npm install -g cash on my Ubuntu box with node 5.3. It seems pretty cool! I couldn't get any support for globbing, however. Not sure if this is a bug, or if it hasn't been implemented yet. I saw that you're using the glob module in package.json, but I was surprised that the CLI didn't offer support for it.

This adds the export command (man page) into the mix.

Similar to how cash $ alias foo ls succeeds (when it wouldn't succeed in bash), cash $ export FOO $PATH also succeeds in redefining FOO to be $PATH.

This exports to process.env, which is case insensitive on Windows (even for the new attributes I'm adding). So, on Windows, you can do things like:

cash $ export FOO='hello'
cash $ echo $foo
hello

I don't think there's any good way to avoid this behavior, so until it's a problem, I suggest it be kept.

This doesn't replace regular assignment. In bash, you can do non-exported assignment of the form: foo=bar, creating a variable named foo with the value "bar". I couldn't figure out a way to write the syntax for regular assignment (posted issue #42 for this).

@dthree do you have any suggestions for additional tests? I modeled unit tests off the ones for alias.

Typically I avoid bring up the tired discussion of "you might not need underscore," but this project boasts being "written in pure ES6." That being said, when searching through some of the source code I discovered some basic usages of lodash. Curiosity got the best of me so I grepped this directory for usages of lodash and found the following unique cases

_.extend
_.filter
_.isArray
_.isObject
_.isString
_.map
_.remove
_.toArray

Usages of extend, filter, isArray, map, remove, and toArray can be replaced by built-in features of JavaScript (some much older than ES6). The others (isString and isObject) have simple, one line equivalents. Are you opposed to removing lodash and using the builtin features? If you're okay with it, I'd can submit a PR.

This should be done on both:

• [x] Travis CI
• [x] Appveyor

This should be a very easy change, and it's pretty low-priority. I can knock this out next week, but if anyone else would like to handle it, I can review. I'm self-assigning so I don't forget about it, but ping this thread if you'd like to take it on.

When I type $ vim or $ vim filename, the shell hangs for a few seconds then the window title changes to [NO NAME] - VIM or filename - VIM but vim doesn't open and I can't enter anything into the shell, ctrl+c does nothing. Have I done something wrong or is there an issue here? Possibly related to the node modules hanging to?

This is related to #22. I noticed that ced6ce6233ebeaa6fa3a82248df83547991fb665 adds support for Windows environment variables, but not for Unix environment variables. This should add that support (although it's not perfect).

On Unix, if you reference a variable that doesn't exist, it usually defaults to the empty string. So echo $FOO would normally print the empty string. I wrote this to parse similarly.

This supports the syntax echo $PATH and echo ${PATH}. It doesn't do any of the tricky string manipulation syntax bash offers though.

I didn't add any tests because I wasn't sure where to add them. If you could point me toward the right spot, I can add those back in. Also, if there's any other issues, I'll gladly do my best to address them.

Fixes #51 and #69 (since they were related).

Run commands with the -c option:

> cash -c 'echo hello world'
hello world
>

Run scripts like so:

> cash helloWorldScript.sh
Hello world!

Also, this adds in the beginning of local variables. This sets the $0, $1, etc. variables as local variables. These variables still aren't exposed to the user, but I can add that functionality in pretty easily by refactoring the preparser a little bit.

Not sure how to describe it, so subject might be incorrect.

Basically what I'm thinking is somewhat like below

> cash ls
execute ls, then exit to original shell
>

> cash cp src dest
copy...
> 

let allow invoke specific command. Is there way without installing as global viacash-global?

External commands were previously limited to Windows. There's no good reason for this, so this adds support for Linux as well.

Fixes #122 Test: manually tried whoami and git status Test: manually tried a not-found command, verified output looks good

When installing cash-touch

sudo npm install cash-touch -g -force

and running

> touch --help

I get this error:

Missing required argument. Showing Help:

sage: touch [options] <files...>

  Options:

    --help                  output usage information
    -a                      change only the access time
    -c, --no-create         do not create any files
    -d, --date [STRING]     parse STRING and use it instead of current time
    -m                      change only the modification time
    -r, --reference [FILE]  use this file's times instead of current time
    --time [WORD]           change the specified time: WORD is access, atime, or use: equivalent to -a WORD is modify or mtime: equivalent to -m

and it shows the help that is not the /dist/help/touch.js file.

This error only affects touch, from what I can tell

When running cat --help, I get a Node.js error.

This error appears on all cash programs, and seems to be related to the parser.

Error:

(node:13969) UnhandledPromiseRejectionWarning: undefined
(node:13969) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:13969) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

This is an investigatory PR to study the introduction of a POSIX compliant shell code parser using bash-parser.

I studied the cash workflow, and I think the majority of changes in source code would concern Vorpal.

They could be implemented directly there (in vorpal core) or we could patch vorpal and implement it only for cash.