Sponsored Content
Full Discussion: Controlling user input
Top Forums Shell Programming and Scripting Controlling user input Post 303038269 by Neo on Thursday 29th of August 2019 09:14:11 AM
Old 08-29-2019
Quote:
Originally Posted by darwin_886
Works great in ubuntu linux with bash 5.0.3(1)-release. Thanks both!
I also tested the script and it worked fine for me on Ubuntu.

Code:
ubuntu:/tmp# read --help
read: read [-ers] [-a array] [-d delim] [-i text] [-n nchars] [-N nchars] [-p prompt] [-t timeout] [-u fd] [name ...]

Seemed to "kinda work" on macOS if I changed the -N to -n but then seemed to have an issue with the -t option so I moved on to other tasks.

Code:
mojave_10_14_6:tmp $ read --help
-bash: read: --: invalid option
read: usage: read [-ers] [-u fd] [-t timeout] [-p prompt] [-a array] [-n nchars] [-d delim] [name ...]

Glad you got it working darwin_886.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Getting user input

I am trying to create a shell (ksh) which has two "read" commands, one which reads a line from a file and another which is inside a loop that reads user input from a keyboard. However, the "read" command inside the loop uses the input from the file and it does not get the user input from keyboard.... (3 Replies)
Discussion started by: stevefox
3 Replies

2. UNIX for Dummies Questions & Answers

accept user input?

how would i accept user input from the keyboard? (2 Replies)
Discussion started by: JamieMurry
2 Replies

3. Shell Programming and Scripting

Question about user input

Hello all, How can i have a user input that reads like this: echo -n "Please enter a & b:" 10 20 read a read b echo $a echo $b 10 20 right now i have divided it into two echos, like echo -n "a: " echo -n "b: " (1 Reply)
Discussion started by: rrahmegni
1 Replies

4. UNIX for Dummies Questions & Answers

Validating user input

I'm trying to set up a script that takes user input and validates that the user input was entered correctly. So far I have this: while : do echo "Please enter your name." read NAME if then echo "You have not entered a name." echo... (13 Replies)
Discussion started by: fufaso
13 Replies

5. Shell Programming and Scripting

User input - Perl need Help

If I want all user input to start with " : " if not display error or what I asking is how to do if statement that control a first letter of string that we want to start with. and not worry about the rest Thank (1 Reply)
Discussion started by: guidely
1 Replies

6. Shell Programming and Scripting

How to get the user input recursively until the user provides valid input

Hi, echo "Enter file name of input file list along with absolute path : " read inputFileList if then for string in `cat inputFileList` do echo $string done else echo " file does not exist" fi From the above code, if the user enters a invalid file... (1 Reply)
Discussion started by: i.srini89
1 Replies

7. Shell Programming and Scripting

Script interacts with user , based on user input it operates

i have a script which takes input from user, if user gives either Y/y then it should continue, else it should quit by displaying user cancelled. #!/bin/sh echo " Enter your choice to continue y/Y OR n/N to quit " read A if then echo " user requested to continue " ##some commands... (7 Replies)
Discussion started by: only4satish
7 Replies

8. Shell Programming and Scripting

How to validate user's input..?

$Input_filename=$ARGV; if (!-d $Input_filename && ! -e $Input_filename) { print "USAGE: Please enter '$ABCD/def/dsed.txt' as an arguement \n"; exit; } 1. Input Is suppose to be something like "$ABCD/def/dsed.txt". if the input is wrong the script should throw an ERROR message.... (2 Replies)
Discussion started by: Rashid Khan
2 Replies

9. Red Hat

"rhgb quiet" controlling the display of commands in single user mode ?"rhgb quiet" controlling the d

Why does removing "rhgb quiet" from the kernel boot parameters control whether or not the commands I enter are displayed in single user mode ? For instance, if I do not remove "rhgb quiet", when I am in single user mode, whatever command I type will not be displayed on the screen. The... (0 Replies)
Discussion started by: Hijanoqu
0 Replies

10. Shell Programming and Scripting

User input and run awk using the input

I am trying to allow a user to enter in text and then store that text in a variable $gene to run in an awk command in which those values are used to run some calculations. I am getting syntax errors however, when I try. Thank you :). The awk runs great if it is a pre-defined file that is used,... (7 Replies)
Discussion started by: cmccabe
7 Replies
Env::PS1(3pm)						User Contributed Perl Documentation					     Env::PS1(3pm)

NAME
Env::PS1 - prompt string formatter SYNOPSIS
# use the import function use Env::PS1 qw/$PS1/; $ENV{PS1} = 'u@h $ '; print $PS1; $readline = <STDIN>; # or tie it yourself tie $prompt, 'Env::PS1', 'PS1'; # you can also tie a scalar ref $format = 'u@h$ '; tie $prompt, 'Env::PS1', $format; DESCRIPTION
This package supplies variables that are "tied" to environment variables like 'PS1' and 'PS2', if read it takes the contents of the variable as a format string like the ones bash(1) uses to format the prompt. It is intended to be used in combination with the various ReadLine packages. EXPORT
You can request for arbitrary variables to be exported, they will be tied to the environment variables of the same name. TIE
When you "tie" a variable you can supply one argument which can either be the name of an environement variable or a SCALAR reference. This argument defaults to 'PS1'. METHODS
"sprintf($format)" Returns the formatted string. Using this method all the time is a lot less efficient then using the tied variable, because the tied variable caches parts of the format that remain the same anyway. FORMAT
The format is copied mostly from bash(1) because that's what it is supposed to be compatible with. We made some private extensions which obviously are not portable. Note that this is not the prompt format as specified by the posix specification, that would only know "!" for the history number and "!!" for a literal "!". Apart from the escape sequences you can also use environment variables in the format string; use $VAR or "${VAR}". The following escape sequences are recognized: a The bell character, identical to "07" d The date in "Weekday Month Date" format D{format} The date in strftime(3) format, uses POSIX e The escape character, identical to "33" Newline Carriage return s The basename of $0 The current time in 24-hour format, identical to "D{%H:%M:%S}" T The current time in 12-hour format, identical to "D{%I:%M:%S}" @ The current time in 12-hour am/pm format, identical to "D{%I:%M %p}" A The current time in short 24-hour format, identical to "D{%H:%M}" u The username of the current user w The current working directory W The basename of the current working directory $ "#" for effective uid is 0 (root), else "$" dd The character corresponding to the octal number 0dd \ Literal backslash H Hostname, uses Sys::Hostname h First part of the hostname l The basename of the (output) terminal device name, uses POSIX, but won't be really portable. [ ] These are used to encapsulate a sequence of non-printing chars. Since we don't need that, they are removed. Extensions The following escapes are extensions not supported by bash, and are not portable: L The (output) terminal device name, uses POSIX, but won't be really portable. C{colour} Insert the ANSI sequence for named colour. Known colours are: black, red, green, yellow, blue, magenta, cyan and white; background colours prefixed with "on_". Also known are reset, bold, dark, underline, blink and reverse, although the effect depends on the terminla you use. Unless you want the whole commandline coloured you should end your prompt with "C{reset}". Of course you can still use the "raw" ansi escape codes for these colours. Note that "bold" is sometimes also known as "bright", so "C{bold,black}" will on some terminals render dark grey. If the environment variable "CLICOLOR" is defined but false colours are switched off automaticly. P{format} Proc information. All of these are unix specific %a Acpi AC status '+' or '-' for connected or not, linux specific %b Acpi battery status in mWh, linux specific %L Load average %l First number of the load average %t Acpi temperature, linux specific %u Uptime %w Number of users logged in Not implemented escapes The following escapes are not implemented, because they are application specific. j The number of jobs currently managed by the application. v The version of the application. V The release number of the application, version + patchelvel ! The history number of the next command. This escape gets replaced by literal '!' while a literal '!' gets replaces by '!!'; this makes the string a posix compatible prompt, thus it will work if your readline module expects a posix prompt. # The command number of the next command (like history number, but minus the lines read from the history file). Customizing If you want to overload escapes or want to supply values for the application specific escapes you can put them in %Env::PS1::map, the key is the escape letter, the value either a string or a CODE ref. If you map a CODE ref it normally is called every time the prompt string is read. When the escape is followed by an argument in the format string (like "D{argument}") the CODE ref is called only once when the string is cached, but in that case it may in turn return a CODE ref. BUGS
Please mail the author if you encounter any bugs. AUTHOR
Jaap Karssenberg || Pardus [Larus] <pardus@cpan.org> This module is currently maintained by Ryan Niebur <rsn@cpan.org> Copyright (c) 2004 Jaap G Karssenberg. All rights reserved. Copyright (c) 2009 Ryan Niebur. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Env, Term::ReadLine::Zoid perl v5.10.0 2009-06-25 Env::PS1(3pm)
All times are GMT -4. The time now is 04:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy