| 1 |
Hi, Alexander. |
| 2 |
|
| 3 |
|
| 4 |
On Sat, 29 Jul 2017 15:08:37 +0300, among other, you wrote: |
| 5 |
|
| 6 |
> > Alright. Here is an example of the problematic line from the point |
| 7 |
> of view of "Gentoo's" bash: |
| 8 |
> |
| 9 |
> read 'Enter device (like /dev/sd(a1,b1,...): ' device |
| 10 |
> |
| 11 |
> Until i remove the brackets, "Gentoo's" bash keeps error messaging. |
| 12 |
> |
| 13 |
> |
| 14 |
> The line from your script above doesn't seem to have a matching right |
| 15 |
> hand side bracket. |
| 16 |
|
| 17 |
Not that i want to discuss the line and the script as whole, but as you |
| 18 |
noticed... |
| 19 |
|
| 20 |
Why it should contain corresponding bracket since it is not code but a |
| 21 |
text string, more over non-interpolated? -- I can write within |
| 22 |
apostrophes anything i want. |
| 23 |
|
| 24 |
Again, bash complains about unacceptable identification, not the number |
| 25 |
of brackets. So, corresponding number of brackets does not solve the |
| 26 |
problem. |
| 27 |
|
| 28 |
> Try running your script in trace mode like so, bash -x script, to |
| 29 |
> further troubleshoot the issue. |
| 30 |
|
| 31 |
Thank you for the point and time, |
| 32 |
Sthu. |
Archives