Closed eno812 closed 8 years ago
This is not usual but it's not a bug of Kint, if you provided more details, I could help you figure it out, what do you mean by call stack?
Hi,
Thanks for your reply but somehow it's not longer a problem. I'm not sure what it was but if it appears again I'll copy the code and ask for your help.
Cheers, Ian
On Tue, Aug 9, 2016 at 5:09 PM, Rokas Šleinius notifications@github.com wrote:
This is not usual but it's not a bug of Kint, if you provided more details, I could help you figure it out, what do you mean by call stack?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/raveren/kint/issues/210#issuecomment-238471795, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5sdtbSjEUKD6INVTSGvJkQeo-iS319ks5qeCe1gaJpZM4JfqQA .
alright, I'm closing the issue then :)
I'm very new to Kint so I'm sure there is an easy explanation for why the output (dump) is happening twice. Once with the call stack and once without.
How do I remove the output without the call stack?