GNU bug report logs - #27901
25.1; x-win-suspend-error: Cannot suspend Emacs while running under X

Previous Next

Package: emacs;

Reported by: Francesco Potortì <Potorti <at> isti.cnr.it>

Date: Tue, 1 Aug 2017 09:03:01 UTC

Severity: minor

Found in version 25.1

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Potorti <at> isti.cnr.it
Cc: 27901 <at> debbugs.gnu.org
Subject: Re: bug#27901: 25.1;
 x-win-suspend-error: Cannot suspend Emacs while running under X
Date: Sat, 05 Aug 2017 22:01:27 +0300
> Date: Sat, 05 Aug 2017 21:43:31 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
> Cc: 27901 <at> debbugs.gnu.org
> 
> > (frame-list)
> > (#<frame emacs <at> tucano.isti.cnr.it 0x116995f8> #<frame F1 0xc41680>)
> > 
> > (next-frame)
> > #<frame F1 0xc41680>
> > 
> > (delete-frame (next-frame))
> > ^^
> > shows the bug (I won't do it now because I am working remotely)
> 
> The F1 frame is a TTY frame, so it sounds like you are trying to
> delete the frame through which you are communicating with Emacs?

Yes, that's what happens here.  From the doc string of next-frame:

  (next-frame &optional FRAME MINIFRAME)

  Return the next frame in the frame list after FRAME.
  It considers only frames on the same terminal as FRAME.
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So you shouldn't use next-frame for this, but instead find the frame
in the list that is other than the selected frame.




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

Previous Next


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