Sun, 29 Jul 2018 15:46:20 +0300 (EEST) Leonid Bobrov
> Lauri, Matthieu, thank you for saving me the trouble having to read and
> understand the code of this big fat hippopotamus.
>
> So, that means somehow I actually accidentally pressed annoying touchpad
> and was lucky enough to click
Lauri, Matthieu, thank you for saving me the trouble having to read and
understand the code of this big fat hippopotamus.
So, that means somehow I actually accidentally pressed annoying touchpad
and was lucky enough to click "Print-All Immediately" without noticing
that... I regret that I've sent
On Sun, Jul 29, 2018 at 08:43:22AM +0200, Matthieu Herrb wrote:
> On Sun, Jul 29, 2018 at 07:28:19AM +0200, Sebastien Marie 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
On Sun, Jul 29, 2018 at 07:28:19AM +0200, Sebastien Marie wrote:
> Hi,
>
> First, thanks to (trying) to search for solve the problem you encountered.
>
> On Sat, Jul 28, 2018 at 10:08:04PM +0300, Leonid Bobrov wrote:
> > Hi!
> >
> > Like I said yesterday, I don't know how to reproduce this bug,
On Sun, Jul 29 2018 07:28:19 +0200, Sebastien Marie wrote:
> personally, I like to know that xterm is unable to create a file.
At least this feature will create files (accessible through the context
menu through ctrl-left click):
Print-All Immediately (resource print-immediate)
Hi,
First, thanks to (trying) to search for solve the problem you encountered.
On Sat, Jul 28, 2018 at 10:08:04PM +0300, Leonid Bobrov wrote:
> Hi!
>
> Like I said yesterday, I don't know how to reproduce this bug, it just
> happened to me and I got this dmesg(1):
> xterm[90461]: pledge
