all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: martin rudalics <rudalics@gmx.at>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Uhm...  weird frame behaviour
Date: Mon, 12 Sep 2011 15:17:54 -0400	[thread overview]
Message-ID: <87obypvacd.fsf@stupidchicken.com> (raw)
In-Reply-To: <4E6E4EC7.8070901@gmx.at> (martin rudalics's message of "Mon, 12 Sep 2011 20:26:15 +0200")

martin rudalics <rudalics@gmx.at> writes:

> Is there a way to get IS_DAEMON in Elisp, `initial-window-system' is
> deprecated AFAICT.

The function `daemonp' is for this.  But I don't think daemon mode has
much to do with this.  The issue is more fundamental:

Firstly, the function window-deletable-p should only look at frames on
the current terminal.  Emacs should never automatically delete the last
frame on a terminal; that is obnoxious.  So other-visible-frames-p needs
to be changed to handle this.  (Not sure why that function is in C, btw;
it could be written in Lisp.)

Secondly, the current code is too aggressive in deciding that a frame
can be deleted.  Consider the following sequence:

C-h k RET
C-x o     => switch to the *Help* window
C-x 5 2   => pop to a new frame displaying *Help*
q         => the frame is deleted

I don't think this is quite right.  The new frame was not created as a
"temporary frame" for displaying the *Help* window, but by the user's
explicit `C-x 5 2' command.  It just so happened that a special-mode
buffer was current at the time.  In this situation, quit-window should
not delete the frame.



  parent reply	other threads:[~2011-09-12 19:17 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10 19:14 Uhm... weird frame behaviour Lars Magne Ingebrigtsen
2011-09-10 22:13 ` Lars Magne Ingebrigtsen
2011-09-11  9:34   ` martin rudalics
2011-09-11 15:27     ` Lars Magne Ingebrigtsen
2011-09-11 15:44       ` Lars Magne Ingebrigtsen
2011-09-12  9:04         ` martin rudalics
2011-09-12  9:04       ` martin rudalics
2011-09-12 12:22         ` Óscar Fuentes
2011-09-12 12:47           ` martin rudalics
2011-09-12 13:32             ` Óscar Fuentes
2011-09-12 14:55               ` martin rudalics
2011-09-12 15:34                 ` Óscar Fuentes
2011-09-12 16:01                   ` Eli Zaretskii
2011-09-12 16:20                     ` Eli Zaretskii
2011-09-12 17:16                       ` Óscar Fuentes
2011-09-12 17:33                         ` Eli Zaretskii
2011-09-12 17:37                         ` Eli Zaretskii
2011-09-12 18:26                       ` martin rudalics
2011-09-12 19:12                         ` Eli Zaretskii
2011-09-13 11:59                           ` martin rudalics
2011-09-12 19:17                         ` Chong Yidong [this message]
2011-09-13 12:00                           ` martin rudalics
2011-09-13 12:45                             ` Óscar Fuentes
2011-09-13 18:28                               ` martin rudalics
2011-09-14  1:34                                 ` Óscar Fuentes
2011-09-13 15:41                             ` Chong Yidong
2011-09-13 18:27                               ` martin rudalics
2011-09-13 19:09                                 ` Chong Yidong
2011-09-12 12:31         ` Óscar Fuentes
2011-09-12 12:47           ` martin rudalics
2011-09-12 13:32         ` Andy Moreton
2011-09-12 13:39           ` Eli Zaretskii
2011-09-12 16:52             ` Lars Magne Ingebrigtsen
2011-09-13 18:28       ` martin rudalics
2011-09-13 20:26         ` Lars Magne Ingebrigtsen
2011-09-10 23:40 ` Rasmus
2011-09-10 23:42   ` Lars Magne Ingebrigtsen
2011-09-10 23:46   ` Rasmus
2011-09-10 23:53     ` Lars Magne Ingebrigtsen
2011-09-11  0:05 ` Óscar Fuentes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87obypvacd.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.