unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: David Kastrup <dak@gnu.org>
Cc: 6861@debbugs.gnu.org
Subject: bug#6861: 24.0.50; Scroll lock not bound
Date: Sat, 10 Aug 2019 21:37:03 +0200	[thread overview]
Message-ID: <CADwFkmndAptPaQU-5ivhA8PiHOh+sAQFMREUU7Sud3jNQRFzFg@mail.gmail.com> (raw)
In-Reply-To: <87r5i02q8w.fsf@lola.goethe.zz>

David Kastrup <dak@gnu.org> writes:

> I tried using the Scroll Lock Key, and got an error telling me it is
> unbound.  I figured out there was a library scroll-lock and loaded it.
> The Scroll Lock Key still was unbound, though calling scroll-lock-mode
> did what I would have expected to be on the scroll lock key.
>
> I suggest putting an appropriate autoloaded default global key
> definition on the Scroll Lock Key, since nothing is gained by not
> binding it to something useful.  If a user happens to have his own
> different definition, this will override the default anyway.

That sounds reasonable to me.  It should be a small job to do it.
Does anyone disagree with such a change?

Thanks,
Stefan Kangas





  reply	other threads:[~2019-08-10 19:37 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 [this message]
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
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=CADwFkmndAptPaQU-5ivhA8PiHOh+sAQFMREUU7Sud3jNQRFzFg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=6861@debbugs.gnu.org \
    --cc=dak@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).