[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Different scan code behavior in X and console

From: 郭晓峰
Subject: Fwd: Different scan code behavior in X and console
Date: Sat, 14 Jan 2012 17:14:15 -0800

Forward a mail I just sent to linux-console@

Any idea on this? If this problem can be resolved, I pretty sure CUA
can be enabled in console mode, including ssh pts.

---------- Forwarded message ----------
From: <>
Date: Sat, Jan 14, 2012 at 4:52 PM
Subject: Different scan code behavior in X and console

Hi there,

Sorry to bother. Not sure whether it is correct to post this question
to the mail list, but can't find a suitable linux console user mail
list for discussing this. If you have good mail list to suggest,
please help me to forward. Thanks!

The question is: I tried to make my emacs have the same key response
on both X and console (ssh pts). However, I can't find scan code for
"Ctrl-PageDown" in console mode. I attached the code for testing the
scan code, and below is different behavior in X and console:

============= X ===========
Press a Key 338   // Just type <PageDown>
Press a Key 27
Press a Key 91
Press a Key 54
Press a Key 59
Press a Key 53
Press a Key 126  // 6-chars for <Ctrl-PageDown>
============ Console =========
Press a Key 338  // Same for <PageDown>
Press a Key         // No response for <Ctrl-PageDown>

Any idea on this? Greatly appreciate your replies, your suggested
readings, and so on!

Best Regards,
Lamu Guo

=============Below is text of the code, for easily reading to skip

#include <stdlib.h>
#include <ctype.h>
#include <curses.h>

int main(void)
 WINDOW *_window = initscr();
 int _rows;
 int _cols;


 /* Accept all keys */
 keypad(_window, true);

 /* Don't echo things that are typed */

 /* Get the screen dimensions */
 getmaxyx(_window, _rows, _cols);

 /* Don't display cursor */

 for (;;)
   printw("Press a Key ");
   int key = wgetch(_window);
   printw("%d \n", key);


 return 0;

Attachment: curin2.c
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]