%n abuse is always so crazy, it is like some developer saw a weird
thing on the shelf and just had to use it.
I am so happy we managed to change the support onto a hard failure.
Jeremie Courreges-Anglas wrote:
> On Mon, Aug 23 2021, George Koehler wrote:
> > Hi,
> >
> > When
On Tue, Aug 24, 2021 at 01:09:14AM +0200, Jeremie Courreges-Anglas wrote:
> On Mon, Aug 23 2021, George Koehler wrote:
> > Hi,
> >
> > When emacs-27.2p1-gtk3 catches a SIGSEGV and is in the foreground of
> > its terminal, then I get a printf %n in /var/log/messages:
> >
> > Aug 23 17:52:26
On Mon, Aug 23 2021, George Koehler wrote:
> Hi,
>
> When emacs-27.2p1-gtk3 catches a SIGSEGV and is in the foreground of
> its terminal, then I get a printf %n in /var/log/messages:
>
> Aug 23 17:52:26 wisconsin emacs: *printf used %n: Fatal error %d: %n%s
>
> I first found this by accident, on
Hi,
When emacs-27.2p1-gtk3 catches a SIGSEGV and is in the foreground of
its terminal, then I get a printf %n in /var/log/messages:
Aug 23 17:52:26 wisconsin emacs: *printf used %n: Fatal error %d: %n%s
I first found this by accident, on OpenBSD/powerpc64, after I made a
wrong diff in my X
