On Tue, Apr 18, 2023 at 11:59:58AM +0000, David wrote: > On Tue, 18 Apr 2023 at 07:51, <to...@tuxteam.de> wrote: > > On Tue, Apr 18, 2023 at 05:29:43AM +0000, David wrote:
[...] > > > The colon and semicolon allow the timestamp > > > to function as a no-operation command. > > > > At least in bash, this doesn't seem necessary, as you are > > only seeing an external representation: internally, bash > > keeps the timestamp separate (as happens to the seq number, > > too). > > Hi, it could well be unnecessary, I haven't played with it > for a long time. [...] > It also would have been several Bash versions ago, Bash 2 or 3, so > perhaps the behaviour changed since I configured it. > > Anyway, if it isn't necessary now, there's no reason for me to advocate > doing that, so I appreciate that you have let everyone know about that. Definitely. I just pointed that out as a request for discussion. Perhaps this isn't portable across shells or even different versions of bash. So caveat emptor :) Cheers and thanks -- I didn't know about HISTTIMEFORMAT before! -- t
signature.asc
Description: PGP signature
