From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Uhm... weird frame behaviour
Date: Mon, 12 Sep 2011 22:12:14 +0300 [thread overview]
Message-ID: <83vcsxwp69.fsf@gnu.org> (raw)
In-Reply-To: <4E6E4EC7.8070901@gmx.at>
> Date: Mon, 12 Sep 2011 20:26:15 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> >> Frames whose names are F1, F2, etc. are terminal frames. Is it
> >> possible that the demonic Emacs doesn't delete the initial terminal
> >> frame, like an otherwise "normal" interactive session would?
> >
> > Answering my own question: yes, that's what happens.
>
> Funny. I thought that
>
> When Emacs is
> invoked with the `--daemon' option, it does not create any initial
> frames, so `initial-window-system' is `nil'.
This describes a different "initial frame", the one that's visible to
the user. See below.
> Does it create a frame afterwards?
No. I was talking about the frame that is created and dumped by
temacs. It is never actually displayed, just used through the initial
part of the startup, and then deleted (except in a daemonic Emacs),
when the "real" initial frame is created.
> > So Martin, I think other_visible_frames should be augmented for the
> > fact that when IS_DAEMON is non-zero, there's one frame that is always
> > there and does not constitute "other frames".
>
> This would break `delete-frame' which apparently _should_ delete a frame
> even if it's the last one in that case.
??? That special frame cannot possibly be deleted anyway, because it
is never displayed. Are we talking about the same thing?
> Is there a way to get IS_DAEMON in Elisp,
Yes, it's called `daemonp'.
next prev parent reply other threads:[~2011-09-12 19:12 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 [this message]
2011-09-13 11:59 ` martin rudalics
2011-09-12 19:17 ` Chong Yidong
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vcsxwp69.fsf@gnu.org \
--to=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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).