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

piped commands are not formatted #17

Closed
Toby-Broom opened this issue Jul 19, 2018 · 4 comments
Closed

piped commands are not formatted #17

Toby-Broom opened this issue Jul 19, 2018 · 4 comments

Comments

@Toby-Broom
Copy link

Hi,

If I write for example:

days=$(echo $1 | perl -ne '/(\d*) day/ && print"$1"')

then the perl -ne is not formatted as expected

Is it possible to make = same class as if, then etc?

how does the recognition of applications work?

@mvdan
Copy link

mvdan commented Jul 22, 2018

Note that this plugin simply wraps shfmt - you should probably open formatting issues over at https://github.com/mvdan/sh.

That said, I don't understand what the bug here is. It would help if you showed what you were expecting.

@Toby-Broom
Copy link
Author

Toby-Broom commented Jul 22, 2018

Sorry here is clarification:

Actual:
actual
Expected:
expected

Could I have = colored too?

expected

@mvdan
Copy link

mvdan commented Jul 22, 2018

I don't think this extension does syntax highlighting. If it did, this bug wouldn't exist - shfmt parses your program just fine.

@Toby-Broom
Copy link
Author

OK thanks for comments, looks like I need a syntax highlight add in then ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants