When print the byte slice, pp print as hex, quite hard to see.

E.g:

pp.Println("65:", []byte{65})

will print:

print:
"65:" []uint8{
  0x41,
}

Expected something like:

"65:" []uint8{
  65,
}

Is this possible and useful?

It would be nice to have a simple way to disable all color (e.g., a function call, or option for New(). The standard way is working fine, though; it's just a nuisance.

Support for customized colors including the ability to mix font and background colors by using a Flag-based description of the colors.

Any questions, thoughts or feedback? :)

Colors are great and make the output very readable, however it's a pain when trying to output to a file

go-isatty[1] seems like it would be a good addition to this project to solve this

[1] https://github.com/mattn/go-isatty

pp write escape sequences into output stream. when the output is not a terminal, i wonder how pp should do work.

• remove escape sequences?
• same as terminal?

I'm thinking pp SHOULD NOT have behavior against whether stdout is terminal or not. So, I want to you to provide A WAY to remove escape sequence for pp, but formatting is enabled.

How do you think?

cause stuff like

&big.Int{
              neg: false,
              abs: big.nat{
                0x908f8474ea971baf,
              },
}

does look too messy to be honest. Also, some default cool things like http response, rsa keys, etc. could be looking more cool (only most popular, much of default types should be printed explicitly)

I wish there is an option / set of methods that will print maps with keys sorted in a best-effort manner. This can be extremely helpful in diffing outputs across runs.

(As you likely know, spew has a SortKeys global config that achieves exactly this.)

Thank you for your consideration.

Experimenting with a fix #53

golfing.org/x/text/message provides a drop in replacement for fmt that can close #53. It seems to be a super clean way of taking care of this and perhaps supporting other localization in the future.

The catch? You get default behavior with %#v, but you do get localization with %d, %f, %v, and possibly others. I'm wondering if this could be an acceptable implementation. We could add an option to set the language, and potentially use alternatives to %#v as needed similar to what was done in #55.

Does this seem like a reasonable way to go?

It seems like it would be a good idea to have an option for a thousands separator for floats and ints, which can make structs with many large numbers easier to read. For example:

myStruct{
  myfloat: 1,000,000.00,
}

What do you think?

Hey,

I am using this to print out deep structures, to filter out some unnecessary structs.

Just sending maybe you would like to merge it. I have not added tests as I am not sure if this is something you would like to merge.

Thanks,

In some case, I'd like to switch on/off to pp's output without changing code.

Golang force me to remove import statement, and unused variables. It's hard for casual use.