mattn/go-shellwords

Issues

• Unexpected output

  #56 opened a year ago by galamit1
  1

• Suggestion: Allow Certain Operators to Be Parsed as Tokens

  #57 opened a year ago by eugene-yzm
  0

• Double-quoted backslash should be preserved

  #52 opened 2 years ago by ndeloof
  0

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

  #54 opened 2 years ago by laurazard
  1

• bug: Parse function removes needed backslashes

  #38 opened 5 years ago by jftuga
  8

• escape from & when parsing shellwords

  #51 opened 2 years ago by bbxwinner
  1

• Some unexpected quote handling behavior when ParseEnv is true

  #48 opened 3 years ago by wtetsu
  1

• ParseEnv problem

  #44 opened 4 years ago by genganpeng
  0

• Default to /bin/sh if SHELL is not set?

  #36 opened 5 years ago by tsarna
  0

• ParseEnv issue

  #16 opened 5 years ago by ayuanx
  0

• Quoted whitespace-only arguments are ignored

  #32 opened 5 years ago by markus-oberhumer
  0

• parsing empty strings

  #5 opened 8 years ago by immesys
  1

• $() not supported

  #20 opened 5 years ago by aplsek
  1

• Multi-commands inside of command substitution are throwing "invalid command line string" errors

  #27 opened 5 years ago by curusarn
  0

• Backtick "eats" all runes until isSpace

  #25 opened 6 years ago by andresvia
  1

• Use custom environment instead of os.Getenv?

  #18 opened 6 years ago by itayd
  4

• panic on > redirection operator

  #14 opened 6 years ago by gromnitsky
  0

• Halp mi

  #10 opened 7 years ago by JohnSmith268
  3

• Thank you!

  #7 opened 7 years ago by inkel
  0

• Create a licence file

  #6 opened 8 years ago by mkumatag
  3

• Update captures `|`

  #4 opened 8 years ago by relvacode
  1

• Escaped spaces at the end

  #3 opened 8 years ago by junegunn
  1

• Support smart quotes

  #2 opened 8 years ago by kegsay
  2