01-21-2009
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My UNIX SA requires that we start in CSH. I like to use KSH because most of my experience is in that shell. I added ksh to the end of my .login script which does take me into KSH but I would like to automatically execute my .profile to setup my aliases.
I cannot use a .shell file because I... (1 Reply)
Discussion started by: veeracer
1 Replies
2. Shell Programming and Scripting
Hey guys,
Hopefully a simple question for you.
In csh I have an alias that looks like:
alias ff 'find . -name \!* -print'
and can therefore perform a search for a file by typing:
ff filename
The same comand does not work in ksh
alias ff="find . -name \!* -print"
I get:
find:... (3 Replies)
Discussion started by: timsk
3 Replies
3. Shell Programming and Scripting
Having been a long-time csh person I now need to convert a lot of stuff to run under ksh. Can anyone tell me how to do a ksh equivalent of the csh history substitution !* that can be used in an alias, ie how would I do:
alias cd "cd \!*; pwd"
alias find "find . -name... (2 Replies)
Discussion started by: jonnywilkins
2 Replies
4. UNIX for Dummies Questions & Answers
I created a simple script and attempted to run it. All that the scrip contained was "ls -l".
At first I received the message "ksh: run_dir: not found"
I then tried typing "csh run_dir" This time the script worked.
typing echo $SHELL produced /bin/ksh
I would like to understand why this... (4 Replies)
Discussion started by: SUSANR9999
4 Replies
5. Shell Programming and Scripting
Ih all,
i have multiples ksh scripts for crontab's unix jobs
they all have same variables declarations and some similar functions
i would have a only single script file to declare my variables, like:
var1= "aaa"
var2= "bbb"
var3= "ccc"
...
function ab { ...}
function bc { ... }... (2 Replies)
Discussion started by: wolfhurt
2 Replies
6. Shell Programming and Scripting
I'm comfortable with csh. However, i need to run a ksh script.Using exec /bin/ksh -i , I'm able to invoke ksh, but the script is not running any further. Variable QDDTS is an env setting on my csh env.
The ksh script goes like this -
#!/bin/csh
exec /usr/local/bin/ksh -i
function... (3 Replies)
Discussion started by: m_shamik
3 Replies
7. Shell Programming and Scripting
Dear friends...
Kindly if any one can help me to know the differences in definning & retreiving data from arrays in the sh,csh & ksh.
I always facing problems in this issue.
thanks...:)
BR (3 Replies)
Discussion started by: ahmad.diab
3 Replies
8. Shell Programming and Scripting
hi, I have a csh script, which has
setenv X xyz etc
My shell is korn
Is there some way I can "source" this to have the variables in my current korn shell?
thanks (3 Replies)
Discussion started by: JamesByars
3 Replies
9. Shell Programming and Scripting
In csh I am using >&. What is the equivalent in ksh??
>& - redirect stdout and stderr (csh,tcsh) (18 Replies)
Discussion started by: kristinu
18 Replies
10. Shell Programming and Scripting
Hi!
I need to translate those line in csh (to initialise variable) into ksh construct.
Any help would be appreciated! I don't know how to replace them :(
Thanks
Hulu
setenv TestHul "$0 $*"
setenv JG `setenvp "JG" "" "$*"`
setenv A_1 `setenvp "A_1" "NA" "$*"`
Please use next time... (2 Replies)
Discussion started by: patator67
2 Replies
LEARN ABOUT CENTOS
xcb_randr_get_screen_resources_crtcs
xcb_randr_get_screen_resources(3) XCB Requests xcb_randr_get_screen_resources(3)
NAME
xcb_randr_get_screen_resources -
SYNOPSIS
#include <xcb/randr.h>
Request function
xcb_randr_get_screen_resources_cookie_t xcb_randr_get_screen_resources(xcb_connection_t *conn, xcb_window_t window);
Reply datastructure
typedef struct xcb_randr_get_screen_resources_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
xcb_timestamp_t timestamp;
xcb_timestamp_t config_timestamp;
uint16_t num_crtcs;
uint16_t num_outputs;
uint16_t num_modes;
uint16_t names_len;
uint8_t pad1[8];
} xcb_randr_get_screen_resources_reply_t;
Reply function
xcb_randr_get_screen_resources_reply_t *xcb_randr_get_screen_resources_reply(xcb_connection_t *conn,
xcb_randr_get_screen_resources_cookie_t cookie, xcb_generic_error_t **e);
Reply accessors
xcb_randr_crtc_t *xcb_randr_get_screen_resources_crtcs(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_crtcs_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_crtcs_end(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_output_t *xcb_randr_get_screen_resources_outputs(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_outputs_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_outputs_end(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_mode_info_t *xcb_randr_get_screen_resources_modes(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_modes_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_randr_mode_info_iterator_t xcb_randr_get_screen_resources_modes_iterator(const xcb_randr_get_screen_resources_reply_t *reply);
uint8_t *xcb_randr_get_screen_resources_names(const xcb_randr_get_screen_resources_request_t *reply);
int xcb_randr_get_screen_resources_names_length(const xcb_randr_get_screen_resources_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_screen_resources_names_end(const xcb_randr_get_screen_resources_reply_t *reply);
REQUEST ARGUMENTS
conn The XCB connection to X11.
window TODO: NOT YET DOCUMENTED.
REPLY FIELDS
response_type
The type of this reply, in this case XCB_RANDR_GET_SCREEN_RESOURCES. 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).
timestamp TODO: NOT YET DOCUMENTED.
config_timestamp
TODO: NOT YET DOCUMENTED.
num_crtcs TODO: NOT YET DOCUMENTED.
num_outputs
TODO: NOT YET DOCUMENTED.
num_modes TODO: NOT YET DOCUMENTED.
names_len TODO: NOT YET DOCUMENTED.
DESCRIPTION
RETURN VALUE
Returns an xcb_randr_get_screen_resources_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_screen_re-
sources_reply.
If you want to handle errors in the event loop instead, use xcb_randr_get_screen_resources_unchecked. See xcb-requests(3) for details.
ERRORS
This request does never generate any errors.
SEE ALSO
AUTHOR
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
XCB
2014-06-10 xcb_randr_get_screen_resources(3)