[chirp_devel] Does the py3 version generate a log file?
If so where can I find it? (on a Mac)
Are you running a frozen build (i.e. the .app) or from the command line? If you run it from the command line, it will log to stdout, but otherwise it will log to ~/.chirp/debug.log (just like the py2 version). For the latter, Help->Show Debug Log. You can also fool it into creating that debug log from the command line by making stdin not a tty:
$ ./chirpwx.py </dev/null
--Dan
On Tue, Dec 13, 2022 at 9:59 AM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
If so where can I find it? (on a Mac)
Are you running a frozen build (i.e. the .app) or from the command line? If you run it from the command line, it will log to stdout, but otherwise it will log to ~/.chirp/debug.log (just like the py2 version). For the latter, Help->Show Debug Log. You can also fool it into creating that debug log from the command line by making stdin not a tty:
$ ./chirpwx.py </dev/null
Are there similar tricks for development using Widows? So far I have been making due with what I see displayed in the terminal window.
Jim KC9HI
On Fri, Dec 23, 2022 at 2:10 PM Dan Smith via chirp_devel chirp_devel@intrepid.danplanet.com wrote:
Are there similar tricks for development using Widows? So far I have been making due with what I see displayed in the terminal window.
That particular trick won't work with windows. Have you tried using "--log log.txt"? I think that should work.
I believe that it does. Thanks!
Jim KC9HI
participants (3)
-
Dan Smith -
Jim Unroe -
Ran Katz