From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: rob.davenport@gmail.com, 28801@debbugs.gnu.org
Subject: bug#28801: 26.0.90; Document after-make-frame-functions, focus-in-hook in Startup Summary node
Date: Fri, 13 Oct 2017 11:40:48 +0300 [thread overview]
Message-ID: <831sm7l9tb.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY1tCnjiuQoAcEqbfGz+HK_mi0NymOFTQNZXFUnNedp5xA@mail.gmail.com> (message from Kaushal Modi on Thu, 12 Oct 2017 21:30:51 +0000)
> Cc: Rob Davenport <rob.davenport@gmail.com>, rob.davenport@gmail.com, eliz@gnu.org
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Thu, 12 Oct 2017 21:30:51 +0000
>
> I have read through (elisp) Startup Summary, but it does not reference after-make-frame-functions and its
> caveat with emacsclient. It also does not reference focus-in-hook.
>
> I believe having that information in that section will be very valuable to other users using emacsclient in GUI
> frame.
These hooks are not related to startup, so I don't see why they should
be described in that section. They would be out of place there, and
the resulting discoverability will be low.
There is a separate section that describes all of the hooks, and I
usually look there when I need some hook, but don't know which one to
use.
There could be a place for a new section in the Emacs manual regarding
customizations for people who start Emacs as a daemon. Patches to
that effect are welcome from people who have experience using and
customizing Emacs in that mode.
next prev parent reply other threads:[~2017-10-13 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 21:30 bug#28801: 26.0.90; Document after-make-frame-functions, focus-in-hook in Startup Summary node Kaushal Modi
2017-10-13 8:40 ` Eli Zaretskii [this message]
2019-10-12 20:31 ` Lars Ingebrigtsen
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=831sm7l9tb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28801@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=rob.davenport@gmail.com \
/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.