tilde creates two logs in every single folder it's run in

I built tilde in arch following the instructions and eventually got it to compile following the instructions (once I figured out what the package names of the dependencies it wanted were.) It seems to work fine, but it creates a log.txt and a libt3widgetlog.txt file in every single folder when I run it. I can't find any setting to disable this, nor does there seem to be a command line parameter. I assume we have to reconfigure it somehow during the build, but the (not) documentation doesn't seem to cover that.

Distro packages that work don't seem to do this. Unfortunately, as mentioned in another issue, the Arch AUR package no longer successfully builds (a bunch of dependencies fail) so I can't test it.

It is definitely not good for it to create such files in every directory you ever run it in. Especially since the log.txt file may well clobber other logs.

[chrisdebian]

Hi, I had a look into this.

libt3widgetlog.txt — found the cause: it's in t3widget's own build, not Tilde or the Arch packaging. Raised separately at gphalkes/t3widget#9 — src/Makefile unconditionally defines -D_T3_WIDGET_DEBUG, with no debug/release toggle, which enables t3widget's own logging permanently.

log.txt — this one's odder. Tilde's own src/log.cc/src/log.h gate this behind #ifdef DEBUG, but Tilde's src/Makefile only ever defines -DTILDE_DEBUG (different macro name). So under a normal build, DEBUG is never defined, and init_log()/lprintf() should expand to no-ops, meaning log.txt shouldn't be created at all. I can't reconcile that with what you're seeing without either the t3shared/makesys build-system repos (which Tilde's Makefile includes but aren't part of this repo) or knowing exactly how the Arch package invokes the build. If you can share the build command or PKGBUILD you used, that would help pin this one down.

Hope the t3widget half is useful as a starting point even though log.txt remains open.