all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Understanding after-make-frame-functions
Date: Wed, 18 May 2016 02:31:09 +0000	[thread overview]
Message-ID: <CAFyQvY1ScSSLHOejk6DYf9RDOnxXDPWP7Mafw4d7S-Qh2PkNJw@mail.gmail.com> (raw)
In-Reply-To: <837fes4ews.fsf@gnu.org>

On Tue, May 17, 2016, 9:59 PM Eli Zaretskii <eliz@gnu.org> wrote:

> When Emacs starts in daemon mode, it doesn't create any frames at all,
> so I don't think I understand what you are saying here.
>

Yup, I messed up the terminology. As I mentioned in my earlier email and
code snippets, my "daemon mode" is "emacsclient -c -a ''". So I run
emacsclient (emacs daemon), but do create a frame using the -c argument.
Please consider all my "emacs daemon" explanation in context of
"emacsclient -c -a ''". In the debug message output (earlier email)
corresponding to this case, you will see that the
after-make-frame-functions hook is called *after* the emacs init is
evaluated.


I think it would be clearer just to say that this hook cannot be used
> for the initial frame.
>

Well, that hook (after-make-frame-functions) is what I can use for the
initial frame in the case of "emacsclient -c -a''&" but never in the case
of "emacs &".

> --

-- 
Kaushal Modi


  reply	other threads:[~2016-05-18  2:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-16 23:35 Understanding after-make-frame-functions Kaushal Modi
2016-05-16 23:42 ` Kaushal Modi
2016-05-17  3:39   ` Eli Zaretskii
2016-05-17  3:44 ` Eli Zaretskii
2016-05-17 16:15   ` Kaushal Modi
2016-05-17 16:36     ` Eli Zaretskii
2016-05-17 18:08       ` Kaushal Modi
2016-05-17 20:18         ` Eli Zaretskii
2016-05-18  2:31           ` Kaushal Modi [this message]
2016-05-18  2:39             ` Eli Zaretskii
2016-05-18  2:46               ` Kaushal Modi

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=CAFyQvY1ScSSLHOejk6DYf9RDOnxXDPWP7Mafw4d7S-Qh2PkNJw@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=eliz@gnu.org \
    --cc=help-gnu-emacs@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.