Sponsored Content
Top Forums Shell Programming and Scripting [SH] Problem reading input in script Post 302469477 by Corona688 on Saturday 6th of November 2010 12:19:36 PM
Old 11-06-2010
Well, what are you typing into the script? How are you running it? Maybe it isn't an editor command.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Reading Input in a Script

#!/usr/bin/sh echo "Enter reason:" echo "> \c" read $reason $reason >> access.log This doesnt work for me. Can someone tell me how I would read the input from what the person types, and then append that to the log file? Regards (2 Replies)
Discussion started by: alwayslearningunix
2 Replies

2. UNIX for Dummies Questions & Answers

Reading input to create a variable in a script?

I would like to prompt for input and then use it as a variable in a script. Something like this. #!/bin/ksh echo "What is your name?: \c" read response echo "Your name is $reply" >file.txt done exit 0 What am I missing? Thanks, (7 Replies)
Discussion started by: darthur
7 Replies

3. Shell Programming and Scripting

Script for reading an input file

#!/bin/sh rpt="/export/home/legato/rpt_offsite"/test_eject.tape cat <$rpt while read line do echo $line perform routine done I am trying to read the contents of this file line by line and perform a routine for each line read. The file contents are numbers.. What is wrong with my... (1 Reply)
Discussion started by: gzs553
1 Replies

4. Shell Programming and Scripting

Reading specific contents from 1 input files and appending it to another input file

Hi guys, I am new to AWK and unix scripting. Please see below my problem and let me know if anyone you can help. I have 2 input files (example given below) Input file 2 is a standard file (it will not change) and we have to get the name (second column after comma) from it and append it... (5 Replies)
Discussion started by: sksahu
5 Replies

5. UNIX for Dummies Questions & Answers

Intermittent problem reading from an input file.

First of all thanks to all for the good post, and the great site. I'm a noob, but I've been able to learna a lot by checking past posts. I haven't been able to make sense of a problem that I've been working on for a while, hopefully someone can help me out. The script I wrote telnets into... (7 Replies)
Discussion started by: Wallygooo32
7 Replies

6. Shell Programming and Scripting

awk script - reading input lines

Can I do something like, if($0==/^int.*$/) { print "Declaration" } for an input like: int a=5; If the syntax is right, it is not working for me, but I am not sure about the syntax. Please help. Thanks, Prasanna (1 Reply)
Discussion started by: prasanna1157
1 Replies

7. Shell Programming and Scripting

Perl Script Not Reading Input Files Correctly

This is one of the strangest things that's happening to me. I'm writing a new Perl script that is trying to read a file. The file is originally in .mof format, but I also saved the contents into a .txt file. As a simple test, I wrote this: #!/user/bin/perl -w use strict; ... (3 Replies)
Discussion started by: kooshi
3 Replies

8. Shell Programming and Scripting

Reading CLI input for script

I've always written scripts where the user executes the script and I prompt them for what they want to do. But I'm trying to write a script where root executes the script 'lock' or its hard-link 'unlock' and the script will passwd -l or passwd -u an account depending on the choice. What would... (3 Replies)
Discussion started by: ADay2Long
3 Replies

9. Shell Programming and Scripting

Problem in reading the input value

echo "Enter the Value : " read value sed '1s:\(.\{6\}\)\(.\{4\}\):\1'$value':' flextran$RUN_DATE-completed.txt > temp.txt mv temp.txt flextran$RUN_DATE-completed.txt on the run time after entering the input value it waits for keystroke and the values is not input to the function The output... (4 Replies)
Discussion started by: rammm
4 Replies

10. Shell Programming and Scripting

Reading user input...problem with tab key

Hi all, I have a little problem with my shell script (reading user input, save user input to variable, invisible characters in the log file :() printf "1. What's your file path?" /path/to/my/file read -e FILE I have invisible characters in my log file (e.g. <ESC> or ^G) when I'm... (3 Replies)
Discussion started by: splendid
3 Replies
PROMPTER(1)							     [nmh-1.5]							       PROMPTER(1)

NAME
prompter - prompting editor front-end for nmh SYNOPSIS
prompter [-erase chr] [-kill chr] [-prepend | -noprepend] [-rapid | -norapid] [-doteof | -nodoteof] file [-version] [-help] DESCRIPTION
Prompter is an editor front-end for nmh which allows rapid composition of messages. This program is not normally invoked directly by users but takes the place of an editor and acts as an editor front-end. It operates on an RFC-822 style message draft skeleton specified by file, normally provided by the nmh commands comp, dist, forw, or repl. Prompter is particularly useful when composing messages over slow network or modem lines. It is an nmh program in that it can have its own profile entry with switches, but it is not invoked directly by the user. The commands comp, dist, forw, and repl invoke prompter as an editor, either when invoked with -editor prompter, or by the profile entry "Editor: prompter", or when given the command edit prompter at the "What now?" prompt. For each empty component prompter finds in the draft, the user is prompted for a response; A <RETURN> will cause the whole component to be left out. Otherwise, a `' preceding a <RETURN> will continue the response on the next line, allowing for multiline components. Continua- tion lines must begin with a space or tab. Each non-empty component is copied to the draft and displayed on the terminal. The start of the message body is denoted by a blank line or a line of dashes. If the body is non-empty, the prompt, which isn't written to the file, is --------Enter additional text or (if -prepend was given) --------Enter initial text Message-body typing is terminated with an end-of-file (usually CTRL-D). With the -doteof switch, a period on a line all by itself also signifies end-of-file. At this point control is returned to the calling program, where the user is asked "What now?". See whatnow (1) for the valid options to this query. By using the -prepend switch, the user can add type-in to the beginning of the message body and have the rest of the body follow. This is useful for the forw command. By using the -rapid switch, if the draft already contains text in the message-body, it is not displayed on the user's terminal. This is useful for low-speed terminals. The line editing characters for kill and erase may be specified by the user via the arguments -kill chr and -erase chr, where chr may be a character; or ` nn', where "nnn" is the octal value for the character. An interrupt (usually CTRL-C) during component typing will abort prompter and the nmh command that invoked it. An interrupt during mes- sage-body typing is equivalent to CTRL-D, for historical reasons. This means that prompter should finish up and exit. The first non-flag argument to prompter is taken as the name of the draft file, and subsequent non-flag arguments are ignored. FILES
$HOME/.mh_profile The user profile /tmp/prompter* Temporary copy of message PROFILE COMPONENTS
prompter-next: To name the editor to be used on exit from .B prompter Msg-Protect: To set mode when creating a new draft SEE ALSO
comp(1), dist(1), forw(1), repl(1), whatnow(1) DEFAULTS
`-prepend' `-norapid' `-nodoteof' CONTEXT
None HELPFUL HINTS
The -rapid option is particularly useful with forw, and -noprepend is useful with comp -use. The user may wish to link prompter under several names (e.g., "rapid") and give appropriate switches in the profile entries under these names (e.g., "rapid: -rapid"). This facilitates invoking prompter differently for different nmh commands (e.g., "forw: -editor rapid"). BUGS
Prompter uses stdio(3), so it will lose if you edit files with nulls in them. MH.6.8 11 June 2012 PROMPTER(1)
All times are GMT -4. The time now is 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy