all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: Initial frame faces
Date: Fri, 24 Jan 2014 11:08:39 +0200	[thread overview]
Message-ID: <83d2jheoh4.fsf@gnu.org> (raw)
In-Reply-To: <52E22697.9000901@yandex.ru>

> Date: Fri, 24 Jan 2014 12:38:47 +0400
> From: Dmitry Antipov <dmantipov@yandex.ru>
> CC: emacs-devel@gnu.org
> 
> Argh, yes (I checked only the case with window system frames). But why
> it is so?  I.e. why the logic should be different between TTY and window
> system frames?  IIUC initial frame is just a stub to provide "something
> looks and behaves like a frame" in batch mode or until the first real frame.

No, initial frame is not a stub.  It is a fully functional TTY frame.
(And what is the difference between a "stub" frame and a "real" frame
anyway?)  It is deleted in the GUI session because it is "no longer
needed" after the first GUI frame is created.

I took that last part in quotes, because it sounds like baggage from
the past, when TTY and GUI frames couldn't co-exist in the same
session.  So we could, for instance, keep that frame around, and reuse
it when the first TTY frame is requested.  Not sure this is wise or
useful, though.

But perhaps we should step back a notch and discuss the original
problem.  What problem(s) did you want to solve, exactly?



  reply	other threads:[~2014-01-24  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24  6:02 Initial frame faces Dmitry Antipov
2014-01-24  7:53 ` Eli Zaretskii
2014-01-24  8:38   ` Dmitry Antipov
2014-01-24  9:08     ` Eli Zaretskii [this message]
2014-01-27  9:51       ` Dmitry Antipov
2014-01-27 16:03         ` Eli Zaretskii

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=83d2jheoh4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    /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.