From: Eli Zaretskii <eliz@gnu.org>
To: larsi@gnus.org, aaronecay@gmail.com
Cc: 21728@debbugs.gnu.org
Subject: bug#21728: 25.0.50; [patch] mention focus-{in,out}-hook in manual
Date: Tue, 23 Feb 2016 19:44:01 +0200 [thread overview]
Message-ID: <83si0jiaou.fsf@gnu.org> (raw)
In-Reply-To: <83bn77ju3q.fsf@gnu.org> (message from Eli Zaretskii on Tue, 23 Feb 2016 17:59:21 +0200)
> Date: Tue, 23 Feb 2016 17:59:21 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: aaronecay@gmail.com, 21728@debbugs.gnu.org
>
> > From: Lars Ingebrigtsen <larsi@gnus.org>
> > Cc: Aaron Ecay <aaronecay@gmail.com>, 21728-done@debbugs.gnu.org
> > Date: Tue, 23 Feb 2016 16:31:47 +1100
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > No, they are also mentioned in the node "Input Focus". And the node
> > > "Focus Events", where you suggested the addition, has a
> > > cross-reference to "Input Focus", near its beginning. So perhaps what
> > > we need is a sentence near that cross-reference that somehow mentions
> > > these two hooks, and all the rest is already in place? Would you like
> > > to suggest an alternative patch along these lines?
> >
> > Hm... is that really necessary, though? With that xref it seems pretty
> > clear that the user should go to that node for more info on everything
> > connected with input focus, I think...
>
> The xref doesn't mention the hooks. I suggested to add a single
> sentence that does, that's all.
Now done on the emacs-25 branch.
prev parent reply other threads:[~2016-02-23 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-21 18:48 bug#21728: 25.0.50; [patch] mention focus-{in,out}-hook in manual Aaron Ecay
2015-10-21 18:57 ` Eli Zaretskii
2016-02-23 5:31 ` Lars Ingebrigtsen
2016-02-23 15:59 ` Eli Zaretskii
2016-02-23 17:44 ` Eli Zaretskii [this message]
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=83si0jiaou.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21728@debbugs.gnu.org \
--cc=aaronecay@gmail.com \
--cc=larsi@gnus.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.