From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: MON KEY Newsgroups: gmane.emacs.bugs Subject: bug#4814: keyboard and system bug with Emacs CVS current through 2009-10-15 on w32 Date: Sun, 15 Aug 2010 19:21:58 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1281915539 3142 80.91.229.12 (15 Aug 2010 23:38:59 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 15 Aug 2010 23:38:59 +0000 (UTC) Cc: ml@g.nevcal.com, 4814@debbugs.gnu.org, 4836@debbugs.gnu.org To: Jason Rumney Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Aug 16 01:38:57 2010 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Okmn3-0006mX-5Q for geb-bug-gnu-emacs@m.gmane.org; Mon, 16 Aug 2010 01:38:57 +0200 Original-Received: from localhost ([127.0.0.1]:58016 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Okmn2-0003ZW-ET for geb-bug-gnu-emacs@m.gmane.org; Sun, 15 Aug 2010 19:38:56 -0400 Original-Received: from [140.186.70.92] (port=51815 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Okmmv-0003Yq-27 for bug-gnu-emacs@gnu.org; Sun, 15 Aug 2010 19:38:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Okmmt-00076Z-5s for bug-gnu-emacs@gnu.org; Sun, 15 Aug 2010 19:38:48 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:41066) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Okmmt-00076T-1q for bug-gnu-emacs@gnu.org; Sun, 15 Aug 2010 19:38:47 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1OkmWg-0006Nn-JP; Sun, 15 Aug 2010 19:22:02 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: Resent-From: MON KEY Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 15 Aug 2010 23:22:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 4814 X-GNU-PR-Package: emacs,w32 X-GNU-PR-Keywords: Original-Received: via spool by 4814-submit@debbugs.gnu.org id=B4814.128191446524523 (code B ref 4814); Sun, 15 Aug 2010 23:22:02 +0000 Original-Received: (at 4814) by debbugs.gnu.org; 15 Aug 2010 23:21:05 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OkmVl-0006NU-91 for submit@debbugs.gnu.org; Sun, 15 Aug 2010 19:21:05 -0400 Original-Received: from mail-ww0-f46.google.com ([74.125.82.46]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OkmVh-0006Mz-Bj; Sun, 15 Aug 2010 19:21:02 -0400 Original-Received: by wwe15 with SMTP id 15so2789748wwe.15 for ; Sun, 15 Aug 2010 16:21:58 -0700 (PDT) Original-Received: by 10.216.7.8 with SMTP id 8mr1943276weo.0.1281914518610; Sun, 15 Aug 2010 16:21:58 -0700 (PDT) Original-Received: by 10.216.65.140 with HTTP; Sun, 15 Aug 2010 16:21:58 -0700 (PDT) X-Google-Sender-Auth: fZgqREO08xkw4TywJtz7jH1lbtU X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Sun, 15 Aug 2010 19:22:02 -0400 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:39510 Archived-At: Hi Jason, > but could this be related to bug#4836? The short answer is: Feel free to close bug#8814 and/or fold it in with bug#4836 if this is what is needed to continue the ongoing development progress of Emacs. The long answer is: I'm not sure if the two are related, though it did occur to me when I read the bug#4836 report (filed on Fri, 30 Oct 2009 three days subsequent to the Oct 27, 2009 filing of bug#4814) that the two _may be_ related. FWIW I had assumed that they were and would eventually be folded together. This said, unfortunately (and largely due to bug#4814/4836), I am no longer using Emacs on w32 systems (or w32 systems in general)... the nature of the problem posed such serious functionality issues w/ integration of Emacs on my w32's as to render the combination useless. As such, I am not able (nor am I now willing) to re-examine the issue. If the problem is now fixed this is good to hear, if not, you will have to find other users better able to clearly describe the impact and nature of the problems made manifest by these bugs esp. given the following: > You don't explain the problem you are seeing clearly, Jason, no offense, but this is BS (and a cop out) and I take some degree of displeasure in pointing out that; - Your recent follow up to bug#4814 was not cc'd to me; - The bug report in question is now nearly 10 months old; - The nature of the bug wasn't/isn't a clearly describable problem. - The affected builds in question are now 13, 14, and 8 months old respectively; - As noted above I am not now willing/able to further troubleshoot the problem This said, I _did_ make multiple follow up reports over an extended period w/re the bug and have not until now received any further requests for additional information. Likewise, I tested multiple different builds (at least five over an eight month period) and made a cumulative report on my findings in an attempt to lend some clarity to the problem. Moreover, I did my best to indicate (and document) specifically that the problem did appear (at least to me) to involve: - 0x2ed76000 control key events; - changes in `local-function-key-map', submaps, and associated event-modifiers; - curious differences between the composition and and length of `input-decode-map'; Specifically my comparison/contrasting of this build known (by me) to pose the problem: ,---- | | - "GNU Emacs 23.1.91.1 (i386-mingw-nt5.1.2600) | of 2010-01-02 on PRETEST" <- FAILED | `---- with these two builds known to work as expected: ,---- | | - "Emacs 23.1.50.1 (i386-mingw-nt5.1.2600) | of 2009-06-30 on LENNART-69DE564 (patched)" | | - "Emacs 23.1.1 of 2009-07-30 on SOFT-MJASON" | `---- This included my indication that: ,---- | | "The value 0x2ed76000 appears in my dribble-file and recent-keys | output for all ``control'' key presses." | `---- My indication that at some point a change occurred such that; ,---- | | "The value of the map: (0 . [67108896]) in `local-function-key-map' | does not seem to have been present until after 07-2009." | `---- and that this change may have impacted/affected the return values for `input-decode-map' from the Emacs builds (patched and unpatched) of circa June/July 2009 e.g. these two builds: ,---- | | "GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600) | of 2009-07-30 on SOFT-MJASON" | | "In GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600) | of 2009-06-30 on LENNART-69DE564 (patched)" | `---- which each returned as follows for `input-decode-map': ,---- | | input-decode-map | => (keymap) | `---- whereas the 2010-01-02 build e.g.: ,---- | "GNU Emacs 23.1.91.1 (i386-mingw-nt5.1.2600) | of 2010-01-02 on PRETEST" `---- had this return value for `input-decode-map': ,---- | | input-decode-map | => (keymap (27 keymap (C-backspace) (C-delete)) | (C-M-backspace) (C-M-delete) (M-backspace) (M-delete)) | `---- My indication that the significant differences in the size of the `key-translation-map' from the non-functioning version of 2010-01-02 which had a length of 2 as compared with the functioning version of Summer-2009 which were considerably lager. My indication of the significant differences in both the size and structure of the sublists of `local-function-key-map'. With the non-functioning version of 2010-01-22 having a length of 66 and the functioning versions of Summer-2009 having a length of 60. And with the non-functioning version. My provision for the implicitly indicative (though apparently non-obvious) fact, that the size/structure differences of `local-function-key-map' happened to map suspiciously to the differences in length for `input-decode-map'. E.g. that the non-functioning version of 2010-01-02 (which had an `input-decode-map' length of 6) as compared with the functioning versions of Summer-2009 which had an `input-decode-map' containing the single element: (keymap). -- /s_P\