| Re: ncurses on Linux how to capture F1 key? [message #178758 is a reply to message #178756] |
Sun, 29 July 2012 09:54   |
crankypuss
Messages: 147
Registered: March 2011
Karma:
|
Senior Member |
|
|
On 07/28/2012 07:21 AM, J.O. Aho wrote:
> Jerry Stuckle wrote:
>> On 7/28/2012 7:50 AM, crankypuss wrote:
>>> On 07/28/2012 05:45 AM, dickey(at)his(dot)com wrote:
>>>> On Friday, July 27, 2012 12:29:53 PM UTC-4, crankypuss wrote:
>>>> > On 07/27/2012 05:00 AM, dickey(at)his(dot)com wrote:
>>>> >
>>>> >> On Friday, July 27, 2012 6:42:09 AM UTC-4, crankypuss wrote:
>>>> >
>>>> >>> Using the C interface the incantation is "keypad(stdscr,
>>>> >>> TRUE)"
>>>> >
>>>> >>>
>>>> >
>>>> >>> What is the equivalent using the PHP interface to ncurses?
>>>> >
>>>> >>>
>>>> >
>>>> >>> Pressing F1 just brings up gnome help (running in xterm under
>>>> >>> ubuntu 11.10).
>>>> >
>>>> >>
>>>> >
>>>> >> that sounds as if you're using one of the vte-based hacks such as
>>>> >> gnome-terminal,
>>>> >
>>>> >> which hijack some keys - have to fix that by undoing the item in
>>>> >> their respective
>>>> >
>>>> >> setup dialogs.
>>>> >
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > I'm using "xterm" and also on a cli (non-GUI) login... terminal
>>>> > type is
>>>> >
>>>> > either "xterm" or "linux". Less stuff grabbed as Linux console.
>>>> >
>>>> >
>>>> >
>>>> > Any additional pointers/keywords I can use to find out more about
>>>> >
>>>> > "undoing the item"?
>>>>
>>>> On a non-GUI login, I wouldn't expect a help-menu (puzzled there).
>>>> For xterm in a desktop, I suppose it's possible for the window-manager
>>>> to have F1 bound (Mac OS X's settings do this with some of the
>>>> function keys, though I've disabled most of those...).
>>>>
>>>
>>> On the non-GUI login the F1 key is readily available.
>>>
>>> Other keys, like ctl-C and ctl-alt-D are firmly bound.
>>>
>>> Can you offer any information about how to modify this on Linux? I'm
>>> relatively new to Linux and don't know where that is controlled.
>>
>> Try a Linux newsgroup.
>
> Quite bored of crankys posts, so I hope he will not.
That goes both ways.
> I suggest he would
> read documentation for once, if he had done that he may have read the
> following:
>
> Quoted from the ncurses_programming_howto:
You quote the C-language interface documentation. Take a look at the
close-to-nonexistent documentation for the PHP interface sometime.
> Normally the terminal driver buffers the characters a user types until a
> new line or carriage return is encountered. But most programs require
> that the characters be available as soon as the user types them. The
> above two functions are used to disable line buffering. The difference
> between these two functions is in the way control characters like
> suspend (CTRL-Z), interrupt and quit (CTRL-C) are passed to the program.
> In the raw() mode these characters are directly passed to the program
> without generating a signal. In the cbreak() mode these control
> characters are interpreted as any other character by the terminal driver.
The code is running in cbreak() mode.
> I guess his program is waiting for a return which you don't get when you
> just press a function key.
>
> As he is a gnome2 fan boy,
Jump to fewer conclusions. If I were a gnome2 fanboy I'd be using
something like GTK+
> he may need to disable the hot key F1 (if
> it's possible in gnome2, as mr Havoc was so kind and thought the less
> configuration options the less confused would the users be, so you can't
> do half of the stuff you could do in Miguel de Icaza's Gnome).
Indeed, in the Linux newsgroups people "like you" don't even know "if
it's possible in gnome2".
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]