trapping keys


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers trapping keys
Prev   Next
# 1  
Old 04-13-2002
Error trapping keys

how do i trap enter command entered by a user.

actually i am throwing a screen this screen has no input but this screen should be displayes unless and until the user presses the enter key. as the user presses enter key the command prompt should come.

how do i achieve this
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Error Trapping

Hi, I have one shell script as below while read SegList do if test -s ${SourceFile_Path}/${Segment_List_Temp} then ls -r -1 ${FTP_Path}/${SegList}.DAT.${Datelist}.GZ|cut -d '.' -f2>>${SourceFile_Path}/${List_Temp} echo "IF above statment Fail I want to Create Emtpy File How to Trapp... (3 Replies)
Discussion started by: samadhanpatil
3 Replies

2. Shell Programming and Scripting

What are public keys in ssh and how do we create the public keys??

Hi All, I am having knowledge on some basics of ssh and wanted to know what are the public keys and how can we create and implement it in connecting server. Please provide the information for the above, it would be helpful for me. Thanks, Ravindra (1 Reply)
Discussion started by: ravi3cha
1 Replies

3. Shell Programming and Scripting

Trapping exit and continuing

Hello I need to source a script. But that script terminates with a trailing exit. Which exits my script. I'm using bash, and this doesn't work: trap 'echo disabled' EXIT source other_file trap '' EXIT Instead, it calls my trap, but then exits anyway. I could get disgusting and... (4 Replies)
Discussion started by: brsett
4 Replies

4. Shell Programming and Scripting

trapping sftp errors

I'm trying to trap errors in a shell script executing an sftp command this way: /usr/bin/sftp $FTP_USER@$FTP_SERVER <<EOF> $HOME/$ERR_FILE cd $FTP_DIR put $FILE_NAME bye EOF I expect errors to be recorded in $ERR_FILE but they are not. The only thing in the $ERR_FILE is: sftp> sftp>... (2 Replies)
Discussion started by: pochon
2 Replies

5. Shell Programming and Scripting

trapping errors from a sub call

I want to trap any errors from a backup database script and send an email when an error occurs. I can trap command errors and send an email in the following code. My problem occurs if an error occurs in the Maxl script, /opt/hyperion/AnalyticServices/bin/essmsh < MaxlScript.msh..., that is called... (0 Replies)
Discussion started by: t_coop
0 Replies

6. UNIX for Dummies Questions & Answers

trapping errors

I am using unixs script to submit programs (SQRS) and need to trap any time of error that is received once the job finishes. Examples of the type of errors I am getting Error! SQR Failed To Process mkdir: Failed to make directory These are showing up in a log file but I do not want to... (3 Replies)
Discussion started by: TimHortons
3 Replies

7. Shell Programming and Scripting

Trapping $! output

hey all, I have a script that creates and then distributes html files via scp on a 60 second cycle. On occasions the scp will hang and not complete with the cycle. When running the scp command in the back ground it returns the PID. How do I trap $! in the script? job=`echo $!` returns... (2 Replies)
Discussion started by: nhatch
2 Replies

8. Shell Programming and Scripting

Error Trapping

Hi, Can anybody tell me how to error trap an empty line. If i am asked for a password and I hit enter without entering any text, how do i display an error? Thanks Kev (6 Replies)
Discussion started by: kev112
6 Replies

9. UNIX for Dummies Questions & Answers

arrow keys / special keys

how to use the arrow keys in shell scripting. is there any special synatax / command for this. i just want to use the arrow keys for navigation. replies appreciated raguram R (3 Replies)
Discussion started by: raguramtgr
3 Replies

10. Shell Programming and Scripting

Trapping Arrow keys

Hey Guys , How do we trap the arrow keys in shell programming. Or atleast can we read the ascii code of the arrow keys. I want to read the arrow keys pressed by the user and accordingly highlight the corresponding menu option. Is it possible in shell to do so ?? ... (1 Reply)
Discussion started by: nageshrc
1 Replies
Login or Register to Ask a Question
YASR(1) 						      General Commands Manual							   YASR(1)

NAME
yasr (Yet Another Screen Reader) - is an attempt at a lightweight, portable screen reader. SYNOPSIS
yasr [ -C config file ] [ -c ] [ -s synthesizer ] [ -p synthesizer port ] [ program arg1 arg2 ... argN ] DESCRIPTION
yasr is a lightweight, portable screen reader. It works by opening a shell in a pty and intercepting all user input/output, maintaining a window of what should be on the screen by looking at the codes and text sent to the screen. It only requires that the user be able to access the text to speech (TTS) device. yasr was originally designed in conjunction with a Speak-out TTS device. Yasr also attempts to support DEC-Talk, DoubleTalk, Apollo, and ViaVoice Outloud, but more work is needed to get these to work fully. It may be able to work with Emacspeak servers, however. Currently yasr has two sets of keymaps, one for "review mode" (ie, reviewing the screen) and one for the standard mode. Keys defined for the standard mode are checked irrespective of whether the user is in review mode or standard mode, but the review mode keymap is checked first in the former case. OPTIONS
-C config file The configuration file that yasr should use. -c Attempts to emulate bash's -c command. It runs /bin/sh, passing it the arguments that were passed to yasr. -s synthesizer The TTS synthesizer to use in conjunction with yasr. -p synthesizer port The port that the TTS synthesizer is connected to. yasr will also fork and exec a program to run, if it (and any optional command line arguments it needs) are given as the last command line arguments. KEYBOARD SETTINGS
Review mode spacebar Say review cursor position. ^ Move to the first character on the line, and say word. $ Move to the last character on the line, and say word. b Say previous character. c Say character. d Say next character. e Read from cursor to bottom of screen. f Search for text on the screen. < Search from cursor to top of screen, using the previously-entered search string. > Search from cursor to bottom of screen, using the previously-entered search string. k Move up a line and read the line (currently same as up arrow). l Say current line. m Move down a line and read the line (currently same as down arrow). n Bypass (send directly to the application). t Read from top to cursor. w Read entire screen. z Move to beginning of previous word and read the word. x Move to beginning of next word and read the word. up arrow Move to previous line and read the line. down arrow Move to next line and read the line. left arrow Move back one character and read the character. right arrow Move ahead one character and read the character. ( Go to previous paragraph. ) Go to next paragraph. alt-i Reinitialize the synthesizer. ` Read the ASCII value of the current character. Standard mode These keys also work in review mode. ctrl-a Say application cursor position. ctrl-l Say line. ctrl-n Bypass. ctrl-x Flush speech buffer. alt-b Say previous character. alt-c Say chracter. alt-d Say word. alt-e Read cursor to bottom of screen. alt-k Say previous line. alt-l Read line. alt-m Read next line. alt-r Toggle review mode. alt-t Read top to cursor. alt-w Read entire screen. alt-x Silence speech. Like ctrl-x but will continue to be silent until a key is pressed (pressing alt-x a second time will start speech again, for example). ctrl-alt-k Keyboard wizard. Allows the user to move, copy, or delete keybindings from within yasr. ctrl-alt-o Options menu. Allows the user to set options from within yasr. ctrl-alt-s Save configuration to disk. alt-enter Disable yasr. Yasr is silent and ignores all keys when disabled. Press again to re-enable. Note: this key is defined in the [options] section as "DisableKey" FILES
/usr/local/share/yasr/yasr.conf yasr configuration file. AUTHOR
Michael P. Gorse <mgorse@users.sourceforge.net> 16 August 2002 YASR(1)