Bash: Added support for parameters and the java and sysctl commands.

[wangliang181230]

Added support for parameters:

1. -key
2. -key=value
3. --key
4. --key=value
5. --aaa.key
6. --aaa.key=value
7. -XX:xxxxx
8. -XX:xxxxx=value
9. -XX:+xxxxx
10. -XX:+xxxxx=value
11. -XX:-xxxxx
12. -XX:-xxxxx=value

Added more commands:

1. java
2. sysctl

Optimize assign-left:

1. aaa.bbb=111

Display effect:

[github-actions]

JS File Size Changes (gzipped)

A total of 1 files have changed, with a combined diff of +49 B (+1.7%).

file	master	pull	size diff	% diff
components/prism-bash.min.js	2.89 KB	2.94 KB	+49 B	+1.7%

Generated by 🚫 dangerJS against b1570c8

[RunDevelopment]

Thank you for the PR @wangliang181230!

I left you a comment on the assignment token. The addition of sysctl is fine.

However, the docker command additions are incorrect. docker run is not a command. docker is a command and run is just a parameter (that docker just so happens to interpret as a sub command). So while the highlighting might be visually pleasing, I think it is incorrect and should be removed.

Also, please add update the tests. We have over a thousand test files and some of them changed. Please run npm run test:languages -- --update to update them all.

[wangliang181230]

However, the docker command additions are incorrect. docker run is not a command. docker is a command and run is just a parameter (that docker just so happens to interpret as a sub command). So while the highlighting might be visually pleasing, I think it is incorrect and should be removed.

Ok, i will remove the docker command.

Also, please add update the tests. We have over a thousand test files and some of them changed. Please run npm run test:languages -- --update to update them all.

Ok.

[RunDevelopment]

Also, please create a test case for the new parameter token. I appreciate the screenshots, but having this code as tests would be better. Please create the file tests/languages/bash/parameter_feature.test and paste your test code into it. After that, please run npm run test:languages -- --update.

[RunDevelopment]

Thank you @wangliang181230!

To make the CI pass, please run npm run build and commit components/prism-bash.min.js. Then I can merge this PR.

[RunDevelopment]

npm told you the problem:

npm WARN lifecycle The node binary used for scripts is C:\Program Files\nodejs\node.exe but npm is using D:\java\graalvm-ce-java8-20.3.0\jre\languages\js\bin\node.exe itself. Use the --scripts-prepend-node-path option to include the path for the node binary npm was executed with.

What's this strange node program you're using?

[wangliang181230]

Thank you @wangliang181230!

To make the CI pass, please run npm run build and commit components/prism-bash.min.js. Then I can merge this PR.

done.

[RunDevelopment]

That didn't work. You might have accidentally installed the wrong uglify version. Could you try running npm ci && npm run build?

[wangliang181230]

PS E:\Workspace_Java\wangliang181230\prism> npm version
{                          
  prismjs: '1.28.0',       
  npm: '6.14.6',           
  ares: '1.16.0',          
  brotli: '1.0.7',         
  http_parser: '2.9.3',    
  llhttp: '2.1.2',         
  modules: '72',           
  napi: '6',               
  nghttp2: '1.41.0',       
  node: '12.18.4',
  openssl: '1.1.1g',       
  uv: '1.38.0',
  v8: '7.8.279.23-node.39',
  zlib: '1.2.11'
}

[wangliang181230]

That didn't work. You might have accidentally installed the wrong uglify version. Could you try running npm ci && npm run build?

@RunDevelopment
I updated nodejs to the latest version 16.16.0 and run npm run build and succeeded.

[RunDevelopment]

Thank you for contributing @wangliang181230!