Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14577
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: error message for missing fi is not helpful |
| Date | 2018-09-13 16:21 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.747.1536870125.1284.bug-bash@gnu.org> (permalink) |
| References | <12006574-8df4-d613-0603-51b77b703a3d@dwd.de> <3461cc07-6477-234b-83ea-30a6bc0c8d8c@case.edu> <5B99CB6D.5060108@tlinx.org> |
On 9/12/18 10:29 PM, L A Walsh wrote: > I can't speak for formatting or base-specific function usage, but I don't > think there was any of those. > > Anyway, if you store the word in a separate array where the line # > is stored, you _could_ list the matching word, but I suspect just the > line it started on would be enough for most users. > > --- (eoftest.sh) > #!/bin/bash > > if ((1)); then > for i in 1 2 3; do > > > > echo wow > > --- >> ./bash eoftest.sh > eoftest.sh: line 10: syntax error: unexpected end of file from line 4. > > The wording was just what I threw in. I don't _need_ attribution for > this if that makes it easier. I'm sure you noticed that word_lineno isn't set for every compound command and that it's limited. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: error message for missing fi is not helpful Chet Ramey <chet.ramey@case.edu> - 2018-09-13 16:21 -0400
csiph-web