go-shellwords

go-shellwords copied to clipboard

bug: Parse function removes needed backslashes

8

In Windows, backslashes are used at the OS path separator. When I run this code, I get an incorrect result for the value of `cmd`: func main() { sh :=...

jftuga

Avoid treating \ as escape char on Windows

6

Fixes #38 While this is probably not a perfect solution, I think it makes a good start as it makes all tests pass on Windows and fixes the most common...

radeksimko

Add the ability to exclude specific separators from the parsing algor…

1

I have implemented a way for users to exclude specific separators from the parsing algorithm to make this package more versatile and flexible. Logic is based on storing excluded characters...

aTTiny73

Unexpected output

1

Hello, I'm trying to parse the following command: ``` command := "RUN /bin/sh -c echo hi --password "pdhjcrkCHJfSchjd3f837"/ # buildkit" args, err := shellwords.Parse(command) ``` and I'm getting `"RUN", "/bin/sh",...

galamit1

Specifically, I was testing: ``` s := "pg_dump db -U usr -F c > bck.dump" argv, _ := shellwords.Parse(s) for _, v := range argv { println(v) } ``` Which...

eugene-yzm

Parsing parens should not always throw `invalid command line string` error

1

It's not uncommon, in certain scenarios, to use parens inside args. An example can be seen in the [Traefik docs here](https://doc.traefik.io/traefik/providers/docker/#constraints) (click `CLI` and look at the example), where it's...

laurazard

This patch adds `ParseComment` option that tells the parser to trim line comments. * `foo # bar` -> `[foo]` instead of `[foo, #, bar]` [fzf](https://github.com/junegunn/fzf) uses this library to parse...

junegunn