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

issue when formatting the truncate command "> poo.foo" #109

Open
DNACore opened this issue Jul 21, 2020 · 4 comments
Open

issue when formatting the truncate command "> poo.foo" #109

DNACore opened this issue Jul 21, 2020 · 4 comments
Labels
upstream the upstream problem

Comments

@DNACore
Copy link

DNACore commented Jul 21, 2020

the script input

> somefile.log

Expected

> somefile.log

but it is

>somefile.log

and it's a wrong command.

@LeoK80
Copy link

LeoK80 commented Aug 26, 2020

Noticed the same cheeky formatting behaviour here as well. Is there any setting in VSCode we can do to affect this behaviour? Style preferences of sorts?

@LeoK80
Copy link

LeoK80 commented Aug 26, 2020

in VS Code you can set option "shellformat.flag": "keep_padding" in the settings.json which fixes it for me. Not fully tested what other side-effect this might have in terms of keeping padding on things that I probably would like to see truncated.

@DNACore
Copy link
Author

DNACore commented Sep 1, 2020

in VS Code you can set option "shellformat.flag": "keep_padding" in the settings.json which fixes it for me. Not fully tested what other side-effect this might have in terms of keeping padding on things that I probably would like to see truncated.

@LeoK80

I set the option "shellformat.flag": "keep_padding" and found that it can't format the code at all

@foxundermoon foxundermoon added the upstream the upstream problem label Oct 2, 2020
@Makeshift
Copy link

This also breaks things such as

${date +%s}

by turning it into

${date+%s}

Setting "keep_padding" seems to stop this, but also seems to stop pretty much everything else that's useful...

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

No branches or pull requests

4 participants