Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14575 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-09-12 09:35 -0400 |
| Last post | 2018-09-12 09:35 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: error message for missing fi is not helpful Chet Ramey <chet.ramey@case.edu> - 2018-09-12 09:35 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-09-12 09:35 -0400 |
| Subject | Re: error message for missing fi is not helpful |
| Message-ID | <mailman.672.1536759353.1284.bug-bash@gnu.org> |
On 9/12/18 5:17 AM, Manuel Reiter wrote: > Bash Version: 4.4 > Patch Level: 12 > Release Status: release > > ++ Description: > > When an if statement is not terminated by a fi, bash's error message is > not helpful in locating the problem. This is tough to do in a bison-generated parser. If someone would like to build the structures required to keep track of which conditional command the shell is currently parsing, and incorporate that into an error message, I'd be happy to look at it. Chet -- ``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 top | Article view | gnu.bash.bug
csiph-web