Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: [SH] Problem reading input in script
Top Forums Shell Programming and Scripting [SH] Problem reading input in script Post 302469471 by Corona688 on Saturday 6th of November 2010 11:48:11 AM
Old 11-06-2010
I think you've got your brackets backwards. >> tells it to append to the HERE file, not read from a here document. And since it never reads the here document, it just hangs reading on STDIN instead. (For future reference, "hangs" is a much more useful description than "doesn't work", which could mean nearly anything...)

If it ever got beyond that it'd consider 'text' and 'HERE' on subsequent lines to be syntax errors.

So, nearly right. Try:

Code:
#!/bin/s
read text
ex $1 <<HERE
text
HERE

 

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

LEARN ABOUT MOJAVE

doctoc_lang_syntax

doctoc_lang_syntax(n)						Documentation tools					     doctoc_lang_syntax(n)

__________________________________________________________________________________________________________________________________________________

NAME

       doctoc_lang_syntax - doctoc language syntax

DESCRIPTION

       This document contains the formal specification of the syntax of the doctoc markup language, version 1.1 in Backus-Naur-Form. This document
       is intended to be a reference, complementing the doctoc language command reference.  A beginner should read the much more informally  writ-
       ten doctoc language introduction first before trying to understand either this document or the command reference.

FUNDAMENTALS

       In  the broadest terms possible the doctoc markup language is like SGML and similar languages. A document written in this language consists
       primarily of markup commands, with text embedded into it at some places.

       Each markup command is a just Tcl command surrounded by a matching pair of [ and ]. Which commands are available, and their arguments, i.e.
       syntax is specified in the doctoc language command reference.

       In this document we specify first the lexeme, and then the syntax, i.e. how we can mix text and markup commands with each other.

LEXICAL DEFINITIONS

       In the syntax rules listed in the next section

       [1]    <TEXT> stands for all text except markup commands.

       [2]    Any  XXX	stands for the markup command [xxx] including its arguments. Each markup command is a Tcl command surrounded by a matching
	      pair of [ and ]. Inside of these delimiters the usual rules for a Tcl command apply with regard to word quotation, nested  commands,
	      continuation lines, etc.

       [3]    <WHITE> stands for all text consisting only of spaces, newlines, tabulators and the comment markup command.

SYNTAX

       The rules listed here specify only the syntax of doctoc documents. The lexical level of the language was covered in the previous section.

       Regarding the syntax of the (E)BNF itself

       [1]    The construct { X } stands for zero or more occurrences of X.

       [2]    The construct [ X ] stands for zero or one occurrence of X.

       The syntax:

       toc	 = defs
		   TOC_BEGIN
		   contents
		   TOC_END
		   { <WHITE> }

       defs	 = { INCLUDE | VSET | <WHITE> }
       contents  = { defs entry } [ defs ]

       entry	 = ITEM | division

       division  = DIVISION_START
		   contents
		   DIVISION_END

BUGS, IDEAS, FEEDBACK
       This  document,	will  undoubtedly  contain bugs and other problems.  Please report such in the category doctools of the Tcllib SF Trackers
       [http://sourceforge.net/tracker/?group_id=12883].  Please also report any ideas for enhancements you may have.

SEE ALSO

       doctoc_intro, doctoc_lang_cmdref, doctoc_lang_faq, doctoc_lang_intro

KEYWORDS

       doctoc commands, doctoc language, doctoc markup, doctoc syntax, markup, semantic markup

CATEGORY

       Documentation tools

COPYRIGHT

       Copyright (c) 2007-2009 Andreas Kupries <andreas_kupries@users.sourceforge.net>

doctools								1.0						     doctoc_lang_syntax(n)
All times are GMT -4. The time now is 04:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy