Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@epse Could also do that but with the current datasets, it can take days and this way I can keep track of the dates as well!
-
You can set your PS1 to include date and time, or just time, or the $SECONDS variable to always have that info in your prompt. Very useful in tmux/screen sessions or otherwise long-running unattended commands
-
m0nk12465y@Pogromist
On Windows
$~#%!324asdasd#$%aasdfdff#$!$@dasdffasdfa#12$~$%&#% date; command; $~#%!324asdasd#$%aasdfdff#$!$@dasdffasdfa#12$~$%&#% date;
I find windows very disturbing visually, and very annoying to the nervous system. -
@andpeterson
Now say with me 1000 times: I WILL USE DATE BETWEEN COMMANDS..
*When you go to office: start doing job like always and forget the shit about it -
ojrask2915y@netikras how do you handle invocation time with PS1? The timestamp is always when the last command ended. Or just mash enter to get a fresh timestamp? :D
Related Rants
Biggest terminal hack I've discovered till now which is so fucking obvious I can't believe I literally just started using it:
Executing the date command right before and after another command/series of commands to see how long shit takes.
$ date; command or commands; date
This is incredibly useful when rendering loads of data in screen sessions!
I actually feel rather retarded for only thinking of this now.
rant
terminal hack
terminal