RE: Tips on hacking VTE
- From: "Petrin, Benjamin" <b petrin WPI EDU>
- To: Behdad Esfahbod <behdad behdad org>
- Cc: "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: RE: Tips on hacking VTE
- Date: Sun, 20 Mar 2011 21:29:58 -0400
Thanks for this! That did the trick
Best,
Benjamin Petrin
________________________________________
From: Behdad Esfahbod [behdad esfahbod gmail com] on behalf of Behdad Esfahbod [behdad behdad org]
Sent: Wednesday, March 02, 2011 12:56 AM
To: Petrin, Benjamin
Cc: desktop-devel-list gnome org
Subject: Re: Tips on hacking VTE
On 02/27/11 21:17, Petrin, Benjamin wrote:
> 2) The debug messages seem to be going to stderr but VTE forks when it starts and I see nothing on the stderr of the console I launched it from. Is there something I am missing here? If I write using g_print() I can see messages but I'm wondering where all the _vte_debug_print() messages are going. This problem isn't such a big deal since I can still debug in some way but I was curious.
Try setting env var VTE_DEBUG=all.
behdad
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]