Sponsored Content
Full Discussion: features of a new SHELL
Top Forums Shell Programming and Scripting features of a new SHELL Post 302273993 by nsharath on Tuesday 6th of January 2009 11:15:31 AM
Old 01-06-2009
Bug POSIX doubts

hello,
thanks a lot for your reply.It was very informative.I shall surely take your words and do the best that I can.
Can you please forward this post in other forums.You said you will do it.Can you send me the link.I shall go and keep seeing there.

I wanted to know the POSIX stupidities that you were saying.What are the problems we generally face with "POSIX" Smilie
 

8 More Discussions You Might Find Interesting

1. Post Here to Contact Site Administrators and Moderators

V2.2.0 new features?

Neo, can you tell us about some of the new features since the upgrade, or are they mostly "behind the scenes"? (1 Reply)
Discussion started by: PxT
1 Replies

2. UNIX for Advanced & Expert Users

Help with Additional Password Features

Hello: I have a customer who is requesting the following security features on a Solaris 8 system: 1. Password history for the three previous passwords. 2. User account lockout after 3 failed login attempts. Can anyone help provide me with a solution or direction for the above? (1 Reply)
Discussion started by: rambo15
1 Replies

3. AIX

AIX OS Features versus Solaris OS Features

Hi Unix Experts, I like to compile and compare all the features that AIX OS (541L) and Solaris OS (Solaris 10) provide. If somebody can shed on this topic would be highly appreciated. Thank you, Khan (0 Replies)
Discussion started by: hkhan12
0 Replies

4. Windows & DOS: Issues & Discussions

Evaluate uUNIX and MSDOS shell script features

I need to select the main features of shell scripting on UNIX and evaluate their MSDOS equivalent. can anyone suggest some online resources articles anything?? Thanks in advance (0 Replies)
Discussion started by: deemon111
0 Replies

5. UNIX for Dummies Questions & Answers

Shell features ???

Hi Can anybody explain the following shell features with example a) Command line editing b) filename completion c) job control (1 Reply)
Discussion started by: skyineyes
1 Replies

6. UNIX for Dummies Questions & Answers

Features explanation???

HI Can anybody explain following UNIX features? Removable file system Dynamic file space allocation Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies

7. Programming

Unix shell with history features like in bash

hii to all i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here history feature should be like that in bash, when press up key show the previous command typed in console plz be... (1 Reply)
Discussion started by: vipin_jss
1 Replies

8. Ubuntu

useradd - shell missing features after adding user

Hi, I need to create a user from a bash script so i have to use useradd. The problem is that when i create a user with: useradd -d /home/sample -m sample after i login with that user I have no history in bash, path do not appears, i can't use arrows and so on. When I use adduser everything is... (5 Replies)
Discussion started by: ktm
5 Replies
xcb_xkb_get_device_info(3)					   XCB Requests 					xcb_xkb_get_device_info(3)

NAME
xcb_xkb_get_device_info - SYNOPSIS
#include <xcb/xkb.h> Request function xcb_xkb_get_device_info_cookie_t xcb_xkb_get_device_info(xcb_connection_t *conn, xcb_xkb_device_spec_t deviceSpec, uint16_t wanted, uint8_t allButtons, uint8_t firstButton, uint8_t nButtons, xcb_xkb_led_class_spec_t ledClass, xcb_xkb_id_spec_t ledID); Reply datastructure typedef struct xcb_xkb_get_device_info_reply_t { uint8_t response_type; uint8_t deviceID; uint16_t sequence; uint32_t length; uint16_t present; uint16_t supported; uint16_t unsupported; uint16_t nDeviceLedFBs; uint8_t firstBtnWanted; uint8_t nBtnsWanted; uint8_t firstBtnRtrn; uint8_t nBtnsRtrn; uint8_t totalBtns; uint8_t hasOwnState; uint16_t dfltKbdFB; uint16_t dfltLedFB; uint8_t pad0[2]; xcb_atom_t devType; uint16_t nameLen; } xcb_xkb_get_device_info_reply_t; Reply function xcb_xkb_get_device_info_reply_t *xcb_xkb_get_device_info_reply(xcb_connection_t *conn, xcb_xkb_get_device_info_cookie_t cookie, xcb_generic_error_t **e); Reply accessors xcb_xkb_string8_t *xcb_xkb_get_device_info_name(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_name_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_generic_iterator_t xcb_xkb_get_device_info_name_end(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_t *xcb_xkb_get_device_info_btn_actions(const xcb_xkb_get_device_info_request_t *reply); int xcb_xkb_get_device_info_btn_actions_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_action_iterator_t xcb_xkb_get_device_info_btn_actions_iterator(const xcb_xkb_get_device_info_reply_t *reply); int xcb_xkb_get_device_info_leds_length(const xcb_xkb_get_device_info_reply_t *reply); xcb_xkb_device_led_info_iterator_t xcb_xkb_get_device_info_leds_iterator(const xcb_xkb_get_device_info_reply_t *reply); REQUEST ARGUMENTS
conn The XCB connection to X11. deviceSpec TODO: NOT YET DOCUMENTED. wanted TODO: NOT YET DOCUMENTED. allButtons TODO: NOT YET DOCUMENTED. firstButton TODO: NOT YET DOCUMENTED. nButtons TODO: NOT YET DOCUMENTED. ledClass TODO: NOT YET DOCUMENTED. ledID TODO: NOT YET DOCUMENTED. REPLY FIELDS
response_type The type of this reply, in this case XCB_XKB_GET_DEVICE_INFO. This field is also present in the xcb_generic_reply_t and can be used to tell replies apart from each other. sequence The sequence number of the last request processed by the X11 server. length The length of the reply, in words (a word is 4 bytes). deviceID TODO: NOT YET DOCUMENTED. present TODO: NOT YET DOCUMENTED. supported TODO: NOT YET DOCUMENTED. unsupported TODO: NOT YET DOCUMENTED. nDeviceLedFBs TODO: NOT YET DOCUMENTED. firstBtnWanted TODO: NOT YET DOCUMENTED. nBtnsWanted TODO: NOT YET DOCUMENTED. firstBtnRtrn TODO: NOT YET DOCUMENTED. nBtnsRtrn TODO: NOT YET DOCUMENTED. totalBtns TODO: NOT YET DOCUMENTED. hasOwnState TODO: NOT YET DOCUMENTED. dfltKbdFB TODO: NOT YET DOCUMENTED. dfltLedFB TODO: NOT YET DOCUMENTED. devType TODO: NOT YET DOCUMENTED. nameLen TODO: NOT YET DOCUMENTED. DESCRIPTION
RETURN VALUE
Returns an xcb_xkb_get_device_info_cookie_t. Errors have to be handled when calling the reply function xcb_xkb_get_device_info_reply. If you want to handle errors in the event loop instead, use xcb_xkb_get_device_info_unchecked. See xcb-requests(3) for details. ERRORS
This request does never generate any errors. SEE ALSO
AUTHOR
Generated from xkb.xml. Contact xcb@lists.freedesktop.org for corrections and improvements. XCB
2014-06-10 xcb_xkb_get_device_info(3)
All times are GMT -4. The time now is 10:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy