Replies: 1 comment 4 replies
-
Ghostty doesnt really know when a command runs thats entirely done by your shell so it can't just step in a limit text for every command when it doesn't know what commands/processes are. Given that how does ghostty know when to reset truncation and what stops it from truncating user input if the value is low and you are typing a bunch. That would magically make it seem like you are typing nothing If you really want to not mess up your output you should pipe it to a file or something similar |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Occasionally I'll mindlessly run a command that generates way more output than I expected and it ends up occupying my whole scroll history (can't jump to the previous prompt or anything). Any ideas for how one could guard against this?
It would be cool if we could retroactively page the output or something. Being able to just undo my last command (like #3469) would also be an option.
For context, I just had this happen while reading a tcpdump (~3500 lines)
Beta Was this translation helpful? Give feedback.
All reactions