From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22731-done@debbugs.gnu.org
Subject: bug#22731: emacs-25: Double clicks don't get through to C-h c.
Date: Fri, 19 Feb 2016 20:12:20 +0000 [thread overview]
Message-ID: <20160219201220.GE3193@acm.fritz.box> (raw)
In-Reply-To: <831t89t9rg.fsf@gnu.org>
On Fri, Feb 19, 2016 at 09:54:59AM +0200, Eli Zaretskii wrote:
> > Date: Thu, 18 Feb 2016 22:39:29 +0000
> > Cc: 22731@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > The problem also occurs with C-h k. It's easy enough to fix, though:
> Please push to master, and thanks.
Done. Marking the bug as fixed.
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2016-02-19 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 12:17 bug#22731: emacs-25: Double clicks don't get through to C-h c Alan Mackenzie
2016-02-18 16:58 ` Eli Zaretskii
2016-02-18 22:39 ` Alan Mackenzie
2016-02-19 7:54 ` Eli Zaretskii
2016-02-19 20:12 ` Alan Mackenzie [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160219201220.GE3193@acm.fritz.box \
--to=acm@muc.de \
--cc=22731-done@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).