maemo.org Bugzilla – Bug 3073
Can't enter non-alphabetic Control Sequences such as Ctrl-\, Ctrl-[...
Last modified: 2009-09-28 18:43:57 UTC
You need to
before you can comment on or make changes to this bug.
SOFTWARE VERSION: 2.2007.50-2
STEPS TO REPRODUCE THE PROBLEM: Input of <Ctrl><non-alphabetic-char> does not
work, ie., Ctrl-a works, but not Ctrl-\. The last time I recall this working
correctly was under IT OS 2007 version 4.2007.26-8... since and up to the
latest IT OS 2008 I am unable to successfully enter control sequences such as
Ctrl-\ or Ctrl-[ on text apps being run on xterm. This happens only with the
Virtual Keyboard input method. From an external BT keyboard no such problems
Confirmed also in Diablo. This happens also for equivalent codes like '|' and
(which correspond to '\' and '[' when using Control (it just zeros some bits)).
Denis: I assume it's still valid in Fremantle SDK alpha that contains
Unfortunately it's WONTFIX for Diablo but I'd love to help pushing this into
Still valid in 4.1.3 (5.2008.43-7) maemo release
(In reply to comment #2)
> I assume it's still valid in Fremantle SDK alpha that contains
With the information available so far I'm not sure it makes sense for
Fremantle, since the stylus keyboard has been dropped there. Non-alphabetic
Ctrl combinations are extremely cumbersome to enter with the finger keyboard,
and impossible with the hardware keyboard, at least with the Diablo & N810
layouts respectively (Ctrl+handwriting? Don't go there!)
On the other hand, Fremantle osso-xterm still has the Ctrl widget in the
toolbar, although it doesn't appear to do anything in scratchbox (but the only
available input method is from the host machine's keyboard so this may not be
the whole story).
Hopefully the beta will come with some input methods to play with...
I entered Ctrl-\ in the Fremantle X-Terminal.
Output is a black square in the terminal.
Is this expected behaviour?
Ctrl-[ does NOT work by the way.
(In reply to comment #5)
> I entered Ctrl-\ in the Fremantle X-Terminal.
> Output is a black square in the terminal.
> Is this expected behaviour?
In general you can compare on-device input to remote input in an ssh session.
On the shell prompt it shouldn't produce anything. If you run cat first and
then type Ctrl-\ it should send it a SIGQUIT and you should see:
~ $ cat
> Ctrl-[ does NOT work by the way.
On the prompt that shouldn't do anything either but in cat it should display
This works for me in the internal Fremantle version.
Closing as FIXED in Fremantle.
This is a WONTFIX for Diablo as Diablo is in maintenance mode and Nokia will
only provide bugfixes for critical issues if at all.
For your interest the Mer project aims to provide a community backport of
Fremantle for N8x0 devices. See http://wiki.maemo.org/Mer for more information.