countermeasure

6 ms·

31.
by countermeasure 6y ago
I think that hacks are the name of the game when it comes to this sort of thing with Bash, so don't feel bad about that. My solution is very much a hack too.
32.
by countermeasure 6y ago
If I'm understanding it correctly, what this sort of approach will give you is a timestamp in the prompt which is generated when the prompt is printed to the terminal and then doesn't change. The thing is that the prompt might sit
33.
by countermeasure 6y ago
I recommend using both approaches together. With an updating prompt, you can see when a command ran without having to type 'history'. And adding a date/time stamp to history is very useful when you need to go back further - h
34.
by countermeasure 6y ago
Excellent point. Seeing when a command in the history list was run is very useful. My preference is just for a date in the history, rather than date and time. I find that when I'm searching history, date is usually granular enough for
35.
by countermeasure 6y ago
Bash is the only shell I've ever used, but one day when time permits I'm looking forward to taking zsh for a test drive.
36.
by countermeasure 6y ago
For years I wanted a Bash prompt which would show when a command actually ran. I don't mean that it would show the time when the prompt was written to the terminal. That's easy. I mean that it would show the time when the command
37.
When did I run that command? Update your Bash prompt with the command start time(redandblack.io)
305 points by countermeasure 6y ago|77 comments
38.
How to Set Up GrapheneOS(redandblack.io)
1 points by countermeasure 7y ago|0 comments