all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tim Van Holder <tim.vanholder@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 6392@debbugs.gnu.org
Subject: bug#6392: Scroll Lock state was on
Date: Fri, 18 Jun 2010 17:07:53 +0200	[thread overview]
Message-ID: <AANLkTimkLjHLLpxsEuZN5X3rtKkMEOjGdLoggVdI5xLs@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil4Rj2jIOp_aNCyCUI8MnFU2aszZwC0Cc57ZruW@mail.gmail.com>

On 18 June 2010 10:20, Tim Van Holder <tim.vanholder@gmail.com> wrote:
> With this morning's bzr trunk this seems to have gone away; pressing
> the key with Emacs still has the message, but that's perfectly normal.
> The message is no longer issued when switching to/from Emacs, nor when
> starting Emacs with scroll lock enabled.

Looks like I was premature. I just switched to emacs from Vista (a
3270 terminal emulator; probably the reason Scroll Lock is on to begin
with) and it hit the error again.
Given that when I tested it this morning (explicitly
enabling/disabling Scroll Lock via the keyboard) things were working,
it may be specifically related to Scroll Lock being enabled
programmatically. It may also be specific to my use case (i.e. using
Cygwin's X server via SSH tunnelling).
I'll try to do some tests next Monday.





  reply	other threads:[~2010-06-18 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 14:59 bug#6392: 24.0.50; Switching to emacs window reports "<Scroll_Lock> is undefined" Tim Van Holder
2010-06-14  8:34 ` bug#6392: Scroll Lock state was on Tim Van Holder
2010-06-14 13:31   ` Stefan Monnier
2010-06-18  8:20     ` Tim Van Holder
2010-06-18 15:07       ` Tim Van Holder [this message]
2020-01-18  1:14         ` Stefan Kangas
     [not found]           ` <CAKMi--AYZL7zt6HR3tz=E3ifrtnh_afrFD0k2O80entCnO5V4w@mail.gmail.com>
2020-01-18 16:50             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimkLjHLLpxsEuZN5X3rtKkMEOjGdLoggVdI5xLs@mail.gmail.com \
    --to=tim.vanholder@gmail.com \
    --cc=6392@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.