Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bash language does not recognize parameter tokens written in dash-case #3569

Open
windymindy opened this issue Oct 5, 2022 · 0 comments · May be fixed by #3748
Open

bash language does not recognize parameter tokens written in dash-case #3569

windymindy opened this issue Oct 5, 2022 · 0 comments · May be fixed by #3748

Comments

@windymindy
Copy link

Information

  • Language: bash, shell
  • Plugins: none

Description
Multiple word command parameters in hyphen-case are not recognized to be class="token parameter variable" but are treated as plain text.

Code snippet

Test page

The code being highlighted incorrectly.
command --two-words --parameter
reidmv added a commit to reidmv/prism that referenced this issue Nov 3, 2023
Previously, a parameter (flag) such as `curl --upload-file` would not be
properly recognized, because of the hyphen in the parameter name. This
commit causes `--upload-file` to be properly recognized as a parameter.

fixes PrismJS#3569, fixes PrismJS#3696
@reidmv reidmv linked a pull request Nov 3, 2023 that will close this issue
reidmv added a commit to reidmv/prism that referenced this issue Nov 3, 2023
Previously, a parameter (flag) such as `curl --upload-file` would not be
properly recognized, because of the hyphen in the parameter name. This
commit causes `--upload-file` to be properly recognized as a parameter.

fixes PrismJS#3569, fixes PrismJS#3696
reidmv added a commit to reidmv/prism that referenced this issue Nov 3, 2023
Previously, a parameter (flag) such as `curl --upload-file` would not be
properly recognized, because of the hyphen in the parameter name. This
commit causes `--upload-file` to be properly recognized as a parameter.

fixes PrismJS#3569, fixes PrismJS#3696
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant