-
Notifications
You must be signed in to change notification settings - Fork 8.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add timestamp view #9331
Comments
I'm gonna toss this on the backlog, because there's prior art for this. Thanks! |
This comment has been minimized.
This comment has been minimized.
@WesleyM77 The bad news for you is that this ticket has just been added to the Icebox. Based on its name (Icebox), I don't believe this will be implemented any time soon (so maybe several years from now, at best). |
@zadjii-msft woah! Didn't know I could modify the prompt like that! |
@WesleyM77 You may be interested in which is a handy little .cmd script I have for updating the prompt based on branch. Useful if you're using |
(Yes, I know this request is 2.5 years old, but I just ended up here searching for whether this feature existed.) One thing not addressed by the workaround of modifying the prompt is seeing timestamps for lines within outputs of commands. Sure, you get a timestamp as soon as the prompt is written after completion of the command, but that doesn't help for the middle of a long-running command. I did however find some workarounds for this. You need to remember to invoke them when you call you command, but that's good enough for me in most cases. In most *nix shells you can pipe a command into In PowerShell you can create a filter function that can be used the same way. (Found here.) To use either one, you then simply pipe your command into it. |
Description of the new feature/enhancement
iTerm2 has a very nifty functionality where you press a keyboard shortcut and it creates a sort of side-column (think of the line number column or the debugging column in an IDE) where it shows timestamps for all executed commands in its scroll back buffer, plus for all "significant events".
I think, but don't quote me on that, that it also shows timestamps for important events, for example if there's a time interval longer than X and suddenly there's a message, it shows the timestamp for that, too.
It's great for retroactively investigating something, especially if you have to use a shell which doesn't implement more advanced prompt features. Or for long running operations with sudden bursts of activity.
https://iterm2.com/documentation-one-page.html
Proposed technical implementation details (optional)
You press a certain keyboard shortcut/select a menu entry.
An additional column is added to the left of the terminal, containing nicely formatted timestamps, down to the second (maybe millisecond, even?) that shows timestamps for all command executions plus significant events in the entire scrollback buffer, as marked by timing of printing to the screen (pause for longer than Y seconds - maybe make this configurable? - then the next message printed is significant and its timestamp is recorded and shown).
The text was updated successfully, but these errors were encountered: