From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: stefan@marxist.se, 6861@debbugs.gnu.org
Subject: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 17:57:35 +0300 [thread overview]
Message-ID: <837e6yejvk.fsf@gnu.org> (raw)
In-Reply-To: <87lfve7ogb.fsf@fencepost.gnu.org> (message from David Kastrup on Tue, 27 Aug 2019 15:00:36 +0200)
> From: David Kastrup <dak@gnu.org>
> Cc: Stefan Kangas <stefan@marxist.se>, 6861@debbugs.gnu.org
> Date: Tue, 27 Aug 2019 15:00:36 +0200
>
> According to Git's logs, w32-scroll-lock-modifier keyboard support was
> apparently originally contributed by Geoff Voelker in 1999 (he has not
> been active since that year) and subsequently maintained and documented
> by you (last documentation changes in 2016). For better or worse, that
> probably makes you by far the best candidate for documenting (and/or
> possibly even for fixing) the interactions of w32-scroll-lock-modifier
> with default activations of the Scroll Lock keybindings on non-Windows
> systems.
What if the best candidate doesn't necessarily have time for doing
everything for which he/she is the best candidate? Does the best
candidate then get to be able to ask someone else to do it?
next prev parent reply other threads:[~2019-08-27 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 9:13 bug#6861: 24.0.50; Scroll lock not bound David Kastrup
2019-08-10 19:37 ` Stefan Kangas
2019-08-20 17:15 ` Stefan Kangas
2019-08-20 17:54 ` Eli Zaretskii
2019-08-20 18:28 ` Stefan Kangas
2019-08-21 16:49 ` Eli Zaretskii
2019-08-27 12:28 ` Stefan Kangas
2019-08-27 12:40 ` Eli Zaretskii
2019-08-27 13:00 ` David Kastrup
2019-08-27 14:57 ` Eli Zaretskii [this message]
2019-08-27 19:11 ` David Kastrup
2019-08-27 19:21 ` Eli Zaretskii
2019-09-26 17:47 ` Stefan Kangas
2019-09-26 18:00 ` Eli Zaretskii
2019-09-28 11:26 ` Stefan Kangas
2019-09-28 12:14 ` Eli Zaretskii
2019-09-28 13:11 ` Stefan Kangas
2019-10-04 16:05 ` Stefan Kangas
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=837e6yejvk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6861@debbugs.gnu.org \
--cc=dak@gnu.org \
--cc=stefan@marxist.se \
/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).