Skip to content
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.

output nearly unreadable for print_r() command #26

Open
FinlayDaG33k opened this issue Nov 22, 2017 · 3 comments
Open

output nearly unreadable for print_r() command #26

FinlayDaG33k opened this issue Nov 22, 2017 · 3 comments

Comments

@FinlayDaG33k
Copy link

Hii there,

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

I wonder if this could be solved soon?
Cheers

@castarco
Copy link
Contributor

castarco commented Dec 5, 2017

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
Copy link
Contributor

castarco commented Dec 5, 2017

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
Copy link
Author

Bug also seems to affect var_dump().
image

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

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants