cornfeedhobo

@bmeneguele Could you try a work around for me? ```$ git commit -m "\"$(

@bmeneguele Confirmed with a small test: ``` go func TestSSNewLines(t *testing.T) { var got []string fs := NewFlagSet("test", ContinueOnError) fs.StringSliceVar(&got, "ss", []string{}, "") fs.Parse([]string{"--ss", "\"foo\nbar\nbaz\n\""}) t.Logf("%v", got) t.Logf("%v", len(got)) }...

I think this is user error. I would suggest using a lookup instead, and stop relying on passing a pointer around. If someone can present some other use cases for...

@pasamio my point is that this is fundamental to golang, not an error with the package. You are passing around a pointer and expecting it to not be overwritten.

I'm fairly confused by this. Doesn't viper solve all these problems?

@Exagone313 you have to maintain your own image, yes

@cmerkle That's pretty harsh for a problem that's been fixed for months. Please check your install before suggesting someone remove their repo.

@cmerkle I take back my comment. I thought I was still using this plugin and not seeing the error. Instead it looks like I phased it out for a different...

@davidovich fwiw, my fork has a disable help option, and has support for exposing unknowns, and it works with cobra (unit tests are run with my fork in place).

@xvrh > New format can easily be added if this port proves useful. It's useful. What would it take to get other barcode support ported?