On 11/5/19 11:44 AM, Jim Monte wrote:
The availability of the % string only after a command unrelated to it (not
using !??) is executed as shown below is not documented, but it probably
falls under the category of a bug. That is, it seems reasonable that both
echo "!%" commands should behave as the second one does.
[root@localhost ~]# bash
[root@localhost ~]# echo "!%"
bash: !: event not found
If there is no history list, and hence no history entries, there are no
events to find. Hence the error message.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
