Sponsored Content
Top Forums Programming Detecting Keyboard Input without return Post 302117022 by ravneetd on Thursday 10th of May 2007 04:24:10 AM
Old 05-10-2007
Jim,
Two things, firstly I don't want to echo my input on the screen. This seems to do that. Second, I still can't seem to get my output without pressing enter. Another strange thing that I notice is that I need to enter atleast 4 characters (and enter thereafter) to see the output. Does that have to do with stream buffering by any chance? Do I need to set it to unbuffered?

Porter,
I looked up the termios library function which you have suggested. While tcsetattr and tcgetattr seem to work fine, I get a symbol reference error for cfmakeraw. However I tried by directly doing what cfmakeraw does, and that also does not solve my problem.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

suppressing keyboard input

Setup Info: This User Id and Password mention below are being used with the ISQL command to connect to a sybase database so they are likely to not be the same as those that were signed on from the session. Situation: Using a korn shell, the shell prompts for a User Id and Password. During the... (1 Reply)
Discussion started by: anthreedhr
1 Replies

2. Programming

Keyboard Input

Does anyone know how do you determine the user idle time of STDIN in order to log the user out for being idle too long. I would like to write a c program to do this but I it is not clear upon how to determine idle time from keyboard input. I have found that the "who.c" source file uses the last... (4 Replies)
Discussion started by: cpaquette
4 Replies

3. Programming

Detecting if command is waiting for input

Hi, After doing a fork and executing a shell, we execute (third party) commands which are essentially non-interactive. But some of them ask for input, under some (unforeseeable) circumstances. When this happens we go on waiting for output. Their is timeout, of course, but we don't seem to know... (5 Replies)
Discussion started by: slash_blog
5 Replies

4. UNIX for Dummies Questions & Answers

Testing for correct user input from keyboard

What script can I use to catch errors in a shell script if user inputs alpha numeric characters instead on integers from the keyboard? (0 Replies)
Discussion started by: Pauline mugisha
0 Replies

5. Shell Programming and Scripting

Keyboard input question

How would I change up a script that currently has something like: bash script echo what's 1 2 3 4? then using read 1 2 3 4 I type 1 2 3 4. so in the script i can do stuff like echo $1 $2 $3 $4 and such... i was just doing echo "1 2 3 4"|bash script But was wondering how could I... (5 Replies)
Discussion started by: biopulse
5 Replies

6. Shell Programming and Scripting

sed execution with input from keyboard

> sed '' Hello hi Hello output How hi output ^D How > sed should take each line as input, process and output the result. In the above scenario the input is passed from keyboard and the output of 'Hello' as you can see is displayed on the screen after 'hi' is passed as input but not as... (1 Reply)
Discussion started by: loggedin.ksh
1 Replies

7. Shell Programming and Scripting

Input keyboard keys upon program launch

Hey guys, first post! I want to write a script that will wait 1 second and then input the keys CTRL+ALT+J to the application i just opened. The program is dosbox, and thay key combination starts video recording :) I have no idea how to program this, can anyone help please? thanks in advance! (2 Replies)
Discussion started by: brunobliss
2 Replies

8. Shell Programming and Scripting

How to get input from keyboard with watch?

Hello, i`m trying to create an network monitoring script and i dont know how to make affect that script by pressing an key from keyboard and that script runs not in while or for or any other loop, but with bash command watch for example: i have created an file (for example check) with content... (0 Replies)
Discussion started by: bacarrdy
0 Replies

9. Shell Programming and Scripting

Read input from Keyboard, do not proceed if no input

Hi, I am working on a script, which requests users to enter input. Ex: read -p "Please enter your email id:" email I don't want users skipping this entry, this has to be mandatory.I dont want to proceed without input. I can do a check if variable $email is empty and proceed if not.But, i... (7 Replies)
Discussion started by: aravindadla
7 Replies

10. Programming

Simple capturing of keyboard input without interruption

I would like to make a function or command that checks for keyboard input without interrupting the program and exits the program when a key is pressed (perhaps the 'q' key). The program below monitors and prints/executes commands upon a change in primary (mouse selection) or clipboard buffer. If... (4 Replies)
Discussion started by: bedtime
4 Replies
TCSETATTR(3)						   BSD Library Functions Manual 					      TCSETATTR(3)

NAME
cfgetispeed, cfsetispeed, cfgetospeed, cfsetospeed, cfsetspeed, cfmakeraw, cfmakesane, tcgetattr, tcsetattr -- manipulating the termios structure LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <termios.h> speed_t cfgetispeed(const struct termios *t); int cfsetispeed(struct termios *t, speed_t speed); speed_t cfgetospeed(const struct termios *t); int cfsetospeed(struct termios *t, speed_t speed); int cfsetspeed(struct termios *t, speed_t speed); void cfmakeraw(struct termios *t); void cfmakesane(struct termios *t); int tcgetattr(int fd, struct termios *t); int tcsetattr(int fd, int action, const struct termios *t); DESCRIPTION
The cfmakeraw(), cfmakesane(), tcgetattr() and tcsetattr() functions are provided for getting and setting the termios structure. The cfgetispeed(), cfsetispeed(), cfgetospeed(), cfsetospeed() and cfsetspeed() functions are provided for getting and setting the baud rate values in the termios structure. The effects of the functions on the terminal as described below do not become effective, nor are all errors detected, until the tcsetattr() function is called. Certain values for baud rates set in the termios structure and passed to tcsetattr() have special meanings. These are discussed in the portion of the manual page that describes the tcsetattr() function. GETTING AND SETTING THE BAUD RATE
The input and output baud rates are found in the termios structure. The unsigned integer speed_t is typedef'd in the include file <termios.h>. The value of the integer corresponds directly to the baud rate being represented, however, the following symbolic values are defined. #define B0 0 #define B50 50 #define B75 75 #define B110 110 #define B134 134 #define B150 150 #define B200 200 #define B300 300 #define B600 600 #define B1200 1200 #define B1800 1800 #define B2400 2400 #define B4800 4800 #define B9600 9600 #define B19200 19200 #define B38400 38400 #ifndef _POSIX_SOURCE #define EXTA 19200 #define EXTB 38400 #endif /*_POSIX_SOURCE */ The cfgetispeed() function returns the input baud rate in the termios structure referenced by tp. The cfsetispeed() function sets the input baud rate in the termios structure referenced by tp to speed. The cfgetospeed() function returns the output baud rate in the termios structure referenced by tp. The cfsetospeed() function sets the output baud rate in the termios structure referenced by tp to speed. The cfsetspeed() function sets both the input and output baud rate in the termios structure referenced by tp to speed. Upon successful completion, the functions cfsetispeed(), cfsetospeed(), and cfsetspeed() return a value of 0. Otherwise, a value of -1 is returned and the global variable errno is set to indicate the error. GETTING AND SETTING THE TERMIOS STATE
This section describes the functions that are used to control the general terminal interface. Unless otherwise noted for a specific command, these functions are restricted from use by background processes. Attempts to perform these operations shall cause the process group to be sent a SIGTTOU signal. If the calling process is blocking or ignoring SIGTTOU signals, the process is allowed to perform the operation and the SIGTTOU signal is not sent. In all the functions, although fd is an open file descriptor, the functions affect the underlying terminal file, not just the open file description associated with the particular file descriptor. The cfmakeraw() function sets the flags stored in the termios structure to a state disabling all input and output processing, giving a ``raw I/O path'', while the cfmakesane() function sets them to a state similar to those of a newly created terminal device. It should be noted that there is no function to reverse this effect. This is because there are a variety of processing options that could be re-enabled and the correct method is for an application to snapshot the current terminal state using the function tcgetattr(), setting raw or sane mode with cfmakeraw() or cfmakesane() and the subsequent tcsetattr(), and then using another tcsetattr() with the saved state to revert to the previous terminal state. The tcgetattr() function copies the parameters associated with the terminal referenced by fd in the termios structure referenced by tp. This function is allowed from a background process, however, the terminal attributes may be subsequently changed by a foreground process. The tcsetattr() function sets the parameters associated with the terminal from the termios structure referenced by tp. The action argument is created by or'ing the following values, as specified in the include file <termios.h>. TCSANOW The change occurs immediately. TCSADRAIN The change occurs after all output written to fd has been transmitted to the terminal. This value of action should be used when changing parameters that affect output. TCSAFLUSH The change occurs after all output written to fd has been transmitted to the terminal. Additionally, any input that has been received but not read is discarded. TCSASOFT If this value is or'ed into the action value, the values of the c_cflag, c_ispeed, and c_ospeed fields are ignored. The 0 baud rate is used to terminate the connection. If 0 is specified as the output speed to the function tcsetattr(), modem control will no longer be asserted on the terminal, disconnecting the terminal. If zero is specified as the input speed to the function tcsetattr(), the input baud rate will be set to the same value as that specified by the output baud rate. If tcsetattr() is unable to make any of the requested changes, it returns -1 and sets errno. Otherwise, it makes all of the requested changes it can. If the specified input and output baud rates differ and are a combination that is not supported, neither baud rate is changed. Upon successful completion, the functions tcgetattr() and tcsetattr() return a value of 0. Otherwise, they return -1 and the global variable errno is set to indicate the error, as follows: [EBADF] The fd argument to tcgetattr() or tcsetattr() was not a valid file descriptor. [EINTR] The tcsetattr() function was interrupted by a signal. [EINVAL] The action argument to the tcsetattr() function was not valid, or an attempt was made to change an attribute represented in the termios structure to an unsupported value. [ENOTTY] The file associated with the fd argument to tcgetattr() or tcsetattr() is not a terminal. SEE ALSO
tcsendbreak(3), termios(4) STANDARDS
The cfgetispeed(), cfsetispeed(), cfgetospeed(), cfsetospeed(), tcgetattr() and tcsetattr() functions are expected to be compliant with the IEEE Std 1003.1-1988 (``POSIX.1'') specification. The cfmakeraw(), cfmakesane() and cfsetspeed() functions, as well as the TCSASOFT option to the tcsetattr() function are extensions to the IEEE Std 1003.1-1988 (``POSIX.1'') specification. BSD
January 2, 1994 BSD
All times are GMT -4. The time now is 05:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy