The xterm ebuild has logging functionality turned on by default and no option to turn it off without editing the ebuild. I for one don't want my sessions to be logged, esp not by default. Reproducible: Always
I agree that logging by default would be bad, but I'm pretty sure that all the configure option does is to make available the "Log to File" menu option. It doesn't actually log unless you request it. I'm running 255 and stracing xterm showed that the only non-special file it opened for writing was my .bash_history file. If the history is what's bothering you, you can just unset $HISTFILE.
The history file is fine but I've seen a "Xterm.xxx.xxx" log file in my home directory several times after rebooting the machine, it's not there while running xterm. I'm not seeing a menu in xterm, but I'm running windowmaker.
Xterm menus are accessed by control-clicking. The particular one relevant here is control-leftclick. Any chance you're invoking xterm with the -l switch?
No, I run "xterm -bg black -fg white -ls +sb -ut". Ahh ok, I've recompiled xterm without logging so I'm not seeing anything about there now.
Besides the command-line option, it could also be a resource setting, e.g., "logging" or "Logging". (There's also a control sequence which could be compiled in, but it's not set by the configure script - a packager would have had to add that to the ebuild).
I've tried #256 and logging is not enabled by default here. It only started logging when I passed the -l switch to it. I can only assume this is something local the reporter has done...
I have not turned it on, but I haven't seen any logfile for a while. Maybe it was some kind of fluke.
(In reply to comment #7) > I have not turned it on, but I haven't seen any logfile for a while. Maybe it > was some kind of fluke. > closing then, if you find out how and when, please reopen
