On 8/6/16 8:41 AM, Austin Group Bug Tracker wrote:
> It would be really nice to gradually move to a state where all
> this becomes rational - accessing the history event number should be
> achieved
> via a shell variable (or even a new special parameter if desired) rather
> than
> via this abominable ! hack. Shell implementors who currently have this !
> expansion in their shell, please consider providing an alternative, and
> then deprecate use of ! in later versions.
ksh93 has $HISTCMD. I haven't bothered because bash already has other
prompt expansion escape sequences that provide the same information.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
