Matthieu Herrb <matth...@herrb.eu> wrote: > > but to decide, we should know *what* triggered this behaviour. > > Hi, > > After digging a bit, there is at least the 'Print All Immediatly' > function from button 1 menu that will trigger the creation of a file > and violate the pledge. > > see xtermPrintImmediately() in print.c:789. The fopen() itself appears > in charToPrinter() on line 498 of the same file. > > Should this feature be disabled in xterm ?
that's probably the best approach. Our goal is to have the safest xterm possible, rather than an xterm with features used by less than 0.001% of people, perhaps once every few months (I am estimating).
