From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Help using the right hook for loading theme on emacs daemon GUI Date: Fri, 25 Jan 2019 09:13:39 +0200 Message-ID: <83a7jp6wgs.fsf@gnu.org> References: <6c1611672809c8d7b5011edf0d2dd831@webmail.orcon.net.nz> <83va2e6t7r.fsf@gnu.org> <83d0ol7scu.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="252996"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org, kaushal.modi@gmail.com To: Phil Sainty Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 25 08:14:54 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gmvhW-0013hj-Cx for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2019 08:14:54 +0100 Original-Received: from localhost ([127.0.0.1]:39466 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmvhV-0004Ea-5a for ged-emacs-devel@m.gmane.org; Fri, 25 Jan 2019 02:14:53 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:56048) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmvgO-0003Or-DI for emacs-devel@gnu.org; Fri, 25 Jan 2019 02:13:45 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gmvgN-0007Gd-MT; Fri, 25 Jan 2019 02:13:43 -0500 Original-Received: from [176.228.60.248] (port=4980 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gmvgN-0006dg-0N; Fri, 25 Jan 2019 02:13:43 -0500 In-reply-to: (message from Phil Sainty on Fri, 25 Jan 2019 10:16:58 +1300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:232679 Archived-At: > Date: Fri, 25 Jan 2019 10:16:58 +1300 > From: Phil Sainty > Cc: kaushal.modi@gmail.com, emacs-devel@gnu.org > > I was already thinking that the `after-make-frame-functions' docstring > could use some additional information (it seems to be a common point > of confusion when people start using --daemon); and even more so given > this new wrinkle. Feel free to improve the docstring. The existing one is really minimal. > > Note that any functions added to these hooks by your initial file > > are > > usually not run for the initial frame, since Emacs reads the initial > > file only after creating that frame. However, if the initial frame is > > specified to use a separate minibuffer frame (*note Minibuffers and > > Frames::), the functions will be run for both, the minibuffer-less and > > the minibuffer frame. > > (As a tangent, the terminology "initial file" instead of the more > common "init file" is a little jarring. I think it's a simple typo. Someone, perhaps even myself, was using "M-/" to minimize typing, and it picked up the wrong expansion. > The info node should be updated to cover the new behaviour in 27, and > I suggest that the docstrings ought to provide a clear pointer to the > info node as being very important reading regarding when the hooks do > and do not run. I think the docstrings should possibly also replicate > or summarise some of that information; but just ensuring that readers > know there are additional subtleties to understand, and where to read > about them, would be good enough. Feel free to make the documentation better, by all means. It is usually hard to spot places in the manuals that need to be updated because they are indirectly related to some change, without explicitly referring to the symbols involved in the change. So such inaccuracies are usually discovered only when we proofread the manuals in preparation for a release. Which is why having such a proofreading step is important. Thanks.