Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15242 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-07-25 08:32 -0400 |
| Last post | 2019-07-25 08:32 -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: Comment before 'else' on CLI, does not save to history correctly Chet Ramey <chet.ramey@case.edu> - 2019-07-25 08:32 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-07-25 08:32 -0400 |
| Subject | Re: Comment before 'else' on CLI, does not save to history correctly |
| Message-ID | <mailman.2192.1564057957.2688.bug-bash@gnu.org> |
On 7/23/19 9:16 PM, Anthony Thyssen wrote: > OS: Fedora 28, Running on a Dell Latitude E7450 > Standard RPM Package: bash-4.4.23-1.fc28.x86_64 > > > if you type a multi-line if-then-else-fi statement with a command before the else. > Bash does not add a semi-colon before the else when saving to history. > > Type into command line (watch out for no-break-spaces added by mail)... > > > if true > then echo yes > # comment - required to activate bug > else echo no > fi > > this works fine! outputting "yes" > But if you look at the history > > history|grep i\\f|tail -1 > > Returning... > > 830 if true; then echo "yes" else echo "no"; fi Thanks for the report. This was fixed in bash-5.0. -- ``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