[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Comment before 'else' on CLI, does not save to history correctly
From: |
Anthony Thyssen |
Subject: |
Comment before 'else' on CLI, does not save to history correctly |
Date: |
Wed, 24 Jul 2019 01:16:09 +0000 |
Version: bash --version
GNU bash, version 4.4.23(1)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
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
You will see the required ';' before the else is missing.
Meaning if the command is repeated from history it will go wrong.
Producing instead...
yes else echo no
If the comment was not present, the semicolon is added correctly.
Probably effects other muti-line input containing comments too.
Anthony Thyssen, writing shell script since 1988
- Comment before 'else' on CLI, does not save to history correctly,
Anthony Thyssen <=