GNU bug report logs - #6861
24.0.50; Scroll lock not bound

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 6861 in the body.
You can then email your comments to 6861 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: David Kastrup <dak <at> gnu.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.0.50; Scroll lock not bound
Date: Sun, 15 Aug 2010 11:13:03 +0200

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.


In GNU Emacs 24.0.50.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1)
 of 2010-07-12 on lola
Windowing system distributor `The X.Org Foundation', version 11.0.10706000
configured using `configure  '--prefix=/usr/local/emacs' '--without-toolkit-scroll-bars' 'CFLAGS=-O2 -fno-crossjumping -g''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

Major mode: Scheme

Minor modes in effect:
  scroll-lock-mode: t
  diff-auto-refine-mode: t
  global-semanticdb-minor-mode: t
  global-semantic-idle-scheduler-mode: t
  semantic-idle-scheduler-mode: t
  semantic-mode: t
  shell-dirtrack-mode: t
  TeX-PDF-mode: t
  desktop-save-mode: t
  minibuffer-electric-default-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<Scroll_Lock> M-x l o a d - l i <tab> <return> s c 
r o <tab> <tab> l o <tab> <return> <Scroll_Lock> M-x 
s c r o <tab> <tab> l o c <tab> m o <tab> <return> 
<Scroll_Lock> <up> <up> <down> <down> <down> <up> M-x 
r e p o r t - e m <tab> <return>

Recent messages:
Loading scroll-lock...done
Making completion list...
Scroll-Lock mode enabled

Load-path shadows:
None found.

Features:
(shadow emacsbug scroll-lock ispell rect diff-mode semantic/tag-file
jka-compr semantic/tag-write semantic/bovine semantic/wisent/python
semantic/wisent/python-wy semantic/wisent semantic/wisent/wisent
semantic/bovine/scm semantic/bovine/scm-by semantic/db-file cedet-files
semantic/bovine/c semantic/decorate/include semantic/db-find
semantic/db-ref semantic/decorate/mode semantic/decorate pulse
semantic/bovine/c-by semantic/lex-spp semantic/bovine/gcc semantic/dep
semantic/analyze semantic/sort semantic/scope semantic/analyze/fcn
semantic/db-mode semantic/db eieio-base semantic/idle semantic/format
ezimage semantic/tag-ls semantic/ctxt semantic/util-modes semantic/util
semantic semantic/tag semantic/lex semantic/fw eieio mode-local cedet pp
url-mailto url-auth url url-proxy url-privacy url-expand url-methods
url-history url-cookie gnus-dup dabbrev multi-isearch help-mode view
debug sendmail nndoc tramp-imap assoc tramp-gw tramp-gvfs zeroconf
url-util url-parse url-vars dbus xml tramp-fish tramp-smb tramp-cache
tramp-ftp tramp-cmds tramp shell tramp-compat trampver browse-url
canlock sha1 hex-util newcomment gnus-fun gnus-kill qp sort gnus-cite
smiley ansi-color flow-fill mail-extr gnus-async gnus-bcklg gnus-ml
disp-table nnfolder parse-time timezone nnnil pop3 nnml nndraft nnmh
auth-source netrc gnus-agent gnus-srvr gnus-score score-mode nnvirtual
gnus-msg gnus-art mm-uu mml2015 epg-config mm-view smime password-cache
dig mailcap nntp gnus-cache gnus-mlspl gnus-sum nnoo gnus-group
time-date gnus-undo nnmail mail-source format-spec gnus-start gnus-spec
gnus-int gnus-range gnus-win diary-lib diary-loaddefs cal-menu calendar
cal-loaddefs info sh-script executable dired-x dired-aux dired message
rfc822 mml mml-sec mm-decode mm-bodies mm-encode mail-parse rfc2231
rfc2047 rfc2045 ietf-drums mailabbrev gmm-utils mailheader vc-rcs
latexenc preview prv-emacs byte-opt warnings reftex-vcr reftex-dcr
reftex-auc reftex reftex-vars tex-bar toolbar-x noutline outline
font-latex bytecomp byte-compile latex easy-mmode edmacro kmacro
tex-style tex-buf tex-info texinfo tex meta-mode python-21 python
cc-mode cc-fonts cc-menus cc-cmds cc-styles cc-align cc-engine cc-vars
cc-defs vc-git lilypond-mode compile comint regexp-opt ring easymenu
scheme package advice help-fns advice-preload desktop minibuf-eldef gnus
gnus-ems nnheader gnus-util mail-utils mm-util mail-prsvr wid-edit
cus-start cus-load preview-latex tex-site auto-loads server tooltip
ediff-hook vc-hooks lisp-float-type mwheel x-win x-dnd tool-bar dnd
fontset image fringe lisp-mode register page menu-bar rfn-eshadow timer
select scroll-bar mldrag mouse jit-lock font-lock syntax facemenu
font-core frame cham georgian utf-8-lang misc-lang vietnamese tibetan
thai tai-viet lao korean japanese hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese case-table epa-hook
jka-cmpr-hook help simple abbrev loaddefs button minibuffer faces
cus-face files text-properties overlay md5 base64 format env code-pages
mule custom widget hashtable-print-readable backquote
make-network-process dbusbind dynamic-setting system-font-setting
font-render-setting gtk x-toolkit x multi-tty emacs)

-- 
David Kastrup

Message #8 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: David Kastrup <dak <at> gnu.org>
Cc: 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Sat, 10 Aug 2019 21:37:03 +0200

David Kastrup <dak <at> 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

Message #11 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: David Kastrup <dak <at> gnu.org>
Cc: 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 20 Aug 2019 19:15:34 +0200

[Message part 1 (text/plain, inline)]

Stefan Kangas <stefan <at> marxist.se> writes:

> David Kastrup <dak <at> 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?

If there are no objections, I'll install the attached patch in a couple of days.
I've also included a NEWS entry for this change.

Thanks,
Stefan Kangas

[0001-Bind-Scroll-Lock-to-scroll-lock-mode-globally.patch (text/x-patch, attachment)]

Message #16 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: dak <at> gnu.org, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 20 Aug 2019 20:54:11 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Tue, 20 Aug 2019 19:15:34 +0200
> Cc: 6861 <at> debbugs.gnu.org
> 
> > David Kastrup <dak <at> 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?
> 
> If there are no objections, I'll install the attached patch in a couple of days.

What about w32-scroll-lock-modifier?

Message #19 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 20 Aug 2019 20:28:15 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

> > If there are no objections, I'll install the attached patch in a couple of days.
>
> What about w32-scroll-lock-modifier?

I'm unfortunately not familiar with that at all, since I never use
Windows.  Nor do I currently have access to any Windows boxes for
testing.  Would this patch break something on w32, or would it just
not work there?

Thanks,
Stefan Kangas

Message #22 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: dak <at> gnu.org, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Wed, 21 Aug 2019 19:49:47 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Tue, 20 Aug 2019 20:28:15 +0200
> Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
> 
> > What about w32-scroll-lock-modifier?
> 
> I'm unfortunately not familiar with that at all, since I never use
> Windows.  Nor do I currently have access to any Windows boxes for
> testing.  Would this patch break something on w32, or would it just
> not work there?

It might not work if w32-scroll-lock-modifier was customized to have
ScrollLock act as a modifier key.

Message #25 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 14:28:30 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

> > > What about w32-scroll-lock-modifier?
> >
> > I'm unfortunately not familiar with that at all, since I never use
> > Windows.  Nor do I currently have access to any Windows boxes for
> > testing.  Would this patch break something on w32, or would it just
> > not work there?
>
> It might not work if w32-scroll-lock-modifier was customized to have
> ScrollLock act as a modifier key.

Could someone with access to a Windows machine please test this patch?

Thanks,
Stefan Kangas

Message #28 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: dak <at> gnu.org, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 15:40:35 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Tue, 27 Aug 2019 14:28:30 +0200
> Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > > > What about w32-scroll-lock-modifier?
> > >
> > > I'm unfortunately not familiar with that at all, since I never use
> > > Windows.  Nor do I currently have access to any Windows boxes for
> > > testing.  Would this patch break something on w32, or would it just
> > > not work there?
> >
> > It might not work if w32-scroll-lock-modifier was customized to have
> > ScrollLock act as a modifier key.
> 
> Could someone with access to a Windows machine please test this patch?

I can, but I'm not sure I understand what you'd like to test.  With
the default value of w32-scroll-lock-modifier your patch will
definitely work; with w32-scroll-lock-modifier customized to some
modifier, like 'super, it will certainly NOT work.

So I think we need to tell Windows users that this binding won't work
if w32-scroll-lock-modifier was customized to a n on-nil value.  Any
suggestions for where to document that?

Message #31 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: David Kastrup <dak <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Stefan Kangas <stefan <at> marxist.se>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 15:00:36 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Stefan Kangas <stefan <at> marxist.se>
>> Date: Tue, 27 Aug 2019 14:28:30 +0200
>> Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
>> 
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>> 
>> > > > What about w32-scroll-lock-modifier?
>> > >
>> > > I'm unfortunately not familiar with that at all, since I never use
>> > > Windows.  Nor do I currently have access to any Windows boxes for
>> > > testing.  Would this patch break something on w32, or would it just
>> > > not work there?
>> >
>> > It might not work if w32-scroll-lock-modifier was customized to have
>> > ScrollLock act as a modifier key.
>> 
>> Could someone with access to a Windows machine please test this patch?
>
> I can, but I'm not sure I understand what you'd like to test.  With
> the default value of w32-scroll-lock-modifier your patch will
> definitely work; with w32-scroll-lock-modifier customized to some
> modifier, like 'super, it will certainly NOT work.
>
> So I think we need to tell Windows users that this binding won't work
> if w32-scroll-lock-modifier was customized to a n on-nil value.  Any
> suggestions for where to document that?

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.

-- 
David Kastrup

Message #34 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: David Kastrup <dak <at> gnu.org>
Cc: stefan <at> marxist.se, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 17:57:35 +0300

> From: David Kastrup <dak <at> gnu.org>
> Cc: Stefan Kangas <stefan <at> marxist.se>,  6861 <at> 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?

Message #37 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: David Kastrup <dak <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: stefan <at> marxist.se, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 21:11:39 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: David Kastrup <dak <at> gnu.org>
>> Cc: Stefan Kangas <stefan <at> marxist.se>,  6861 <at> 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?

Nobody gets to ask someone else to do anything regarding free software
unless paying them for it.  In the end, that means that most features
and ports get maintained by those interested in the particular port
and/or feature.

The quality of the Windows port, like all ports, stands and falls with
the interest of those investing time and energy into it.  Blocking
useful features for free platforms because of interference with
non-standard settings of Windows-only special features is something that
does not make a lot of sense within the frame of the GNU project.

If you have a concrete proposal of what to do better other than "don't
touch this code", based on your relative acquaintance with it, that
would likely go a long way towards keeping things running also on W32.

-- 
David Kastrup

Message #40 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: David Kastrup <dak <at> gnu.org>
Cc: stefan <at> marxist.se, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Tue, 27 Aug 2019 22:21:52 +0300

> From: David Kastrup <dak <at> gnu.org>
> Cc: stefan <at> marxist.se,  6861 <at> debbugs.gnu.org
> Date: Tue, 27 Aug 2019 21:11:39 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> From: David Kastrup <dak <at> gnu.org>
> >> Cc: Stefan Kangas <stefan <at> marxist.se>,  6861 <at> 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?
> 
> Nobody gets to ask someone else to do anything regarding free software
> unless paying them for it.  In the end, that means that most features
> and ports get maintained by those interested in the particular port
> and/or feature.
> 
> The quality of the Windows port, like all ports, stands and falls with
> the interest of those investing time and energy into it.  Blocking
> useful features for free platforms because of interference with
> non-standard settings of Windows-only special features is something that
> does not make a lot of sense within the frame of the GNU project.
> 
> If you have a concrete proposal of what to do better other than "don't
> touch this code", based on your relative acquaintance with it, that
> would likely go a long way towards keeping things running also on W32.

You've made a huge mountain out of a molehill.  All I did was review a
patch and provide comments to make it better.

Message #43 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Thu, 26 Sep 2019 19:47:50 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

> > Could someone with access to a Windows machine please test this patch?
>
> I can, but I'm not sure I understand what you'd like to test.  With
> the default value of w32-scroll-lock-modifier your patch will
> definitely work; with w32-scroll-lock-modifier customized to some
> modifier, like 'super, it will certainly NOT work.

Got it.

> So I think we need to tell Windows users that this binding won't work
> if w32-scroll-lock-modifier was customized to a n on-nil value.  Any
> suggestions for where to document that?

I'm not so sure what would be a good place to do it.  For starters, I
can't find any reference to w32-scroll-lock-modifier in the manual,
and I'm not sure if that's on purpose.

To my mind, it would be enough to add it to the NEWS entry.
Alternatively, we could add a section on scroll-lock-mode to (info
"(emacs) Auto Scrolling") and document it there.  (Although I'm not
sure it makes sense given that w32-scroll-lock-modifier is not
mentioned anywhere else...)

WDYT?

Best regards,
Stefan Kangas

Message #46 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: dak <at> gnu.org, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Thu, 26 Sep 2019 21:00:09 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Thu, 26 Sep 2019 19:47:50 +0200
> Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
> 
> > So I think we need to tell Windows users that this binding won't work
> > if w32-scroll-lock-modifier was customized to a n on-nil value.  Any
> > suggestions for where to document that?
> 
> I'm not so sure what would be a good place to do it.  For starters, I
> can't find any reference to w32-scroll-lock-modifier in the manual,
> and I'm not sure if that's on purpose.

Try the other manual, emacs.info.

> To my mind, it would be enough to add it to the NEWS entry.

I think it should be in the doc string of that mode as well.

Thanks.

Message #49 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Sat, 28 Sep 2019 13:26:48 +0200

[Message part 1 (text/plain, inline)]

Eli Zaretskii <eliz <at> gnu.org> writes:

> > > So I think we need to tell Windows users that this binding won't work
> > > if w32-scroll-lock-modifier was customized to a n on-nil value.  Any
> > > suggestions for where to document that?
> >
> > I'm not so sure what would be a good place to do it.  For starters, I
> > can't find any reference to w32-scroll-lock-modifier in the manual,
> > and I'm not sure if that's on purpose.
>
> Try the other manual, emacs.info.

Thanks, found it now.  Not sure how I missed it before.

> > To my mind, it would be enough to add it to the NEWS entry.
>
> I think it should be in the doc string of that mode as well.

OK.  How about the attached patch?

Best regards,
Stefan Kangas

[0001-Bind-Scroll_Lock-to-scroll-lock-mode-globally.patch (text/x-patch, attachment)]

Message #52 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: dak <at> gnu.org, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Sat, 28 Sep 2019 15:14:16 +0300

> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Sat, 28 Sep 2019 13:26:48 +0200
> Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
> 
> > > To my mind, it would be enough to add it to the NEWS entry.
> >
> > I think it should be in the doc string of that mode as well.
> 
> OK.  How about the attached patch?

It's fine, but please say "MS-Windows" to be more precise.

Thanks.

Message #55 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Sat, 28 Sep 2019 15:11:59 +0200

[Message part 1 (text/plain, inline)]

Eli Zaretskii <eliz <at> gnu.org> writes:

> > OK.  How about the attached patch?
>
> It's fine, but please say "MS-Windows" to be more precise.

Thanks; fixed in attached patch.  I'll push it in a couple of days if
there are no further comments.

Best regards,
Stefan Kangas

[0001-Bind-Scroll_Lock-to-scroll-lock-mode-globally.patch (text/x-patch, attachment)]

Message #58 received at 6861 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: David Kastrup <dak <at> gnu.org>, 6861 <at> debbugs.gnu.org
Subject: Re: bug#6861: 24.0.50; Scroll lock not bound
Date: Fri, 4 Oct 2019 18:05:39 +0200

close 6861 27.1
quit

> I'll push it in a couple of days if there are no further comments.

Now pushed as commit 591c8bc70f.

Best regards,
Stefan Kangas

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.