Bug#807653: nedit and numeric keypad

2023-04-28 Thread Alex Kent Hajnal
TLDR: Try running "XKB_DISABLE=1 nedit" --- I've investigated a bit more and it looks like the problem resides outside of nedit. I believe I've isolated the source of the problem to libXt, specifically when it is compiled with Xkb support[1]. I've submitted a bug report to libXt but in the

Bug#807653: nedit and numeric keypad

2022-12-17 Thread Alex Kent Hajnal
The tests I've run are interesting: When logged in to my desktop running Ubuntu 22.04.1, Xorg 1:7.7+23ubuntu2 I see the issue for: * nedit run locally * nedit run on my laptop via ssh * nedit run on my server via ssh When logged in to my laptop running Ubuntu 14.04.2, Xorg

Bug#807653: nedit and numeric keypad

2019-04-29 Thread markus
Hello, here a few findings from me: 1) NEdit's text window is different from Motifs text widget. IIRC it was derived from it some long time ago. This is the reason, why it behaves different. 2) I do recall in the early 2000s NEdit had some strange behaviours with CAPS-Lock and Numlock etc, so

Bug#807653: nedit and numeric keypad

2017-10-31 Thread Graham Inggs
Control: notforwarded -1 Control: reassign -1 nedit 1:5.6~cvs20081118-8 Motif upstream closed #1649 INVALID.

Bug#807653: nedit and numeric keypad

2016-04-13 Thread Graham Inggs
On 10 April 2016 at 09:15, Paul Gevers wrote: > On 04-04-16 15:20, Graham Inggs wrote: >> I also noticed in other dialogs in NEdit, for example Search/Find and >> File/Save As... , that the numeric keypad keys behave as expected, >> following NumLock. > > Always, or just with

Bug#807653: nedit and numeric keypad

2016-04-10 Thread Paul Gevers
Hi On 04-04-16 15:20, Graham Inggs wrote: > I also noticed in other dialogs in NEdit, for example Search/Find and > File/Save As... , that the numeric keypad keys behave as expected, > following NumLock. Always, or just with the patch? > I was only able to reproduce the problem in the main >

Bug#807653: nedit and numeric keypad

2016-04-04 Thread Graham Inggs
For what it is worth, the proposed patch attached to upstream's bug, although slightly different to what was eventually applied, behaves in exactly the same way. I also noticed in other dialogs in NEdit, for example Search/Find and File/Save As... , that the numeric keypad keys behave as

Bug#807653: nedit and numeric keypad

2016-03-18 Thread Graham Inggs
Hi Upstream's bug tracker is back online. The problem with the numeric keypad was introduced by the fix to upstream's bug #1300 [1]. You can verify it for yourself by building motif 2.3.4, including the patch below to disable the fix: --- a/lib/Xm/Transltns.c +++ b/lib/Xm/Transltns.c @@ -56,7

Bug#807653: nedit and numeric keypad

2016-03-12 Thread Graham Inggs
The problem seems to have been introduced in Motif 2.3.4. I built (Open)Motif 2.3.3 and the numeric keypad works in nedit. I also tried downloading and installing upstream's Motif 2.3.4-1 binary package [1] and only the 5 key on the numeric pad works in nedit. Unfortunately, upstream's bug

Bug#807653: nedit and numeric keypad

2016-03-09 Thread Graham Inggs
> On 11-12-15 10:44, Orvoine Bertrand wrote: > > When using NEdit, I am unable to use the numeric keypad to enter numbers no > > matter whether the numlock is on or off ( with the exception of key "5") > > I can confirm this behavior. I confirm this behaviour in nedit as well. It doesn't seem to

Bug#807653: nedit and numeric keypad

2016-03-09 Thread Paul Gevers
Control: tags -1 confirmed Control: reassign -1 motif On 11-12-15 10:44, Orvoine Bertrand wrote: > When using NEdit, I am unable to use the numeric keypad to enter numbers no > matter whether the numlock is on or off ( with the exception of key "5") I can confirm this behavior. > If I recompil

Bug#807653: nedit and numeric keypad

2015-12-11 Thread Orvoine Bertrand
Package: nedit Version: 1:5.6~cvs20081118-9 Severity: normal Dear Maintainer, When using NEdit, I am unable to use the numeric keypad to enter numbers no matter whether the numlock is on or off ( with the exception of key "5") wheezy nedit version is ok ( 1:5.6~cvs20081118-7 ) but not after