GNU bug report logs - #29067
26.0.90; "Invalid client frame" when doing save-buffers-kill-terminal

Previous Next

Package: emacs;

Reported by: Kaushal Modi <kaushal.modi <at> gmail.com>

Date: Mon, 30 Oct 2017 17:11:01 UTC

Severity: normal

Found in version 26.0.90

Done: martin rudalics <rudalics <at> gmx.at>

Bug is archived. No further changes may be made.

Full log


Message #20 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Kaushal Modi <kaushal.modi <at> gmail.com>
To: martin rudalics <rudalics <at> gmx.at>
Cc: "bug-gnu-emacs <at> gnu.org" <bug-gnu-emacs <at> gnu.org>,
 Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: 26.0.90;
 "Invalid client frame" when doing save-buffers-kill-terminal
Date: Wed, 01 Nov 2017 13:40:15 +0000
[Message part 1 (text/plain, inline)]
I need to add that I never saw this issue in my emacsclient sessions,
because in my config, I directly call (save-buffers-kill-emacs) if
(daemonp). So the (save-buffers-kill-terminal) never got executed when
running emacsclient with my config.

So I see this issue on emacsclient too if I do
M-x save-buffers-kill-terminal

So need to figure out what could cause that client parameter to be set to
"Unprintable entity".


-- 

Kaushal Modi
[Message part 2 (text/html, inline)]

This bug report was last modified 7 years and 205 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.