output nearly unreadable for `print_r()` command

[FinlayDaG33k]

Hii there,

I've tried using your notebook, but already at the first moment of using it, I found a little inconvenience:

I wonder if this could be solved soon? Cheers

[castarco]

Hi @FinlayDaG33k , I'll check it. I'm sorry for being slow responding here. In fact, I'm currently working on a "workspaces" feature (to manage composer dependencies in a truly isolated way).

When I'll finish with the workspaces work, I'll check this issue.

[castarco]

P.D.: I think that we could "overwrite" the print_r function (creating another one available in the current namespace) producing a nicer output. But this is not a solution for people who calls the function using its fully qualified name \print_r .

[FinlayDaG33k]

Bug also seems to affect var_dump().

For the sake of, I've also tried var_export(), however, it doesn't seem to affect that?

also noticed that both var_dump() and var_export() end with null, while print_r() ends with true.