3 ms·

To add... The missing scrollbars feel painful to me. I don't even want them for scrolling, really. I want the visual reference for: "How much content is in t

To add... The missing scrollbars feel painful to me. I don't even want them for scrolling, really. I want the visual reference for: "How much content is in this window" and "Where am I in that content" I still use it daily but it means I have to switch tools for certain things, and reading log files or log output is one of the more common reasons I switch. I should probably look into trying to get the scrollback info into my statusline, No idea how easy or hard that is - so if someone has done it, feel free to shoot me pointers.

jsrcout 1y ago
Same here, scroll bars are literally the one missing feature keeping me from making Ghostty my daily driver. But the release notes roadmap mentions they will add them for 1.3. Waiting with anticipation.
j1elo 1y ago
Suggestion to use Klogg (https://github.com/variar/klogg https://github.com/variar/klogg) for reading log files. I always was on the camp of "tail -f file.log" but since discovering this app, I saw the light.
- ehaughee 1y ago
  Or lnav (https://lnav.org/ https://lnav.org/).
- fragmede 1y ago
  Centralized logging, a la Splunk is the gold (with what they charge, probably platinum) standard here. Watching someone who knows what they're doing at a Splunk console for a distributed system they understand is a thing of beauty. It's just a shame they charge so much.
godelski 1y ago
Maybe I'm misunderstanding your request but do you not pipe outputs into a pager? (Less, more, batcat, etc) I feel like I'm probably not understanding the context though.
- ec109685 1y ago
  Sometimes you just have a command write output.
  - rorytbyrne 1y ago
    In that case are scroll bars even helpful for determining position? My terminal history is normally huge, and the log output would be some unknown percentage of the total scrollable history.
  - godelski 1y ago
    I'm still not quite sure what you mean. You can still {|,>} output from a program, so less and grep still help. Or do you mean when you inevitably forget? Well then yeah you're at the mercy of your terminal but as others mentioned ghostty has a hack to help as well as some other terminals. But this should also help reinforce why you should pipe more often and write to files (or tee). It sucks but not making the same mistakes in the future and learning better habits will help you write better code and use better practices. But that's the age old problem of "you can't analyze the data you didn't record" and that's a footgun you'll experience in every programming language, every experiment, and across many parts of life. Better to record and throw it away than not record and regret it.
    - horsawlarway 1y ago
      > "you can't analyze the data you didn't record" It IS recorded. It's right there in scrollback (Literally the default buffer to record). It's easily accessible with most tooling, including nice scrolling, mouse support, find/search, etc... Except in Ghostty, it's not so accessible. No find, no scrollbars. I end up having to dump it into another tool, which at least they make pretty easy (ex: https://ghostty.org/docs/config/keybind/reference#write_scrollback_file https://ghostty.org/docs/config/keybind/reference#write_scro...). Although deciding when to do that would be easier if I had a better indicator for just how much scrollback content exists. Ex - if it's 3 pages... I'll just scroll through it. If it's 3000 pages... time to dump to file. So no - by default I use a pager... just about never. Why would I when I have absolutely everything in scrollback by default 99.9% of the time? --- Don't confuse your preferences with "correct" :P I'm doing just fine with code and best practices, I'm simply stating that this is a rough edge on an otherwise lovely tool.

jsrcout 1y ago

Same here, scroll bars are literally the one missing feature keeping me from making Ghostty my daily driver. But the release notes roadmap mentions they will add them for 1.3. Waiting with anticipation.

j1elo 1y ago

Suggestion to use Klogg (https://github.com/variar/klogg https://github.com/variar/klogg) for reading log files. I always was on the camp of "tail -f file.log" but since discovering this app, I saw the light.

ehaughee 1y ago
Or lnav (https://lnav.org/ https://lnav.org/).
fragmede 1y ago
Centralized logging, a la Splunk is the gold (with what they charge, probably platinum) standard here. Watching someone who knows what they're doing at a Splunk console for a distributed system they understand is a thing of beauty. It's just a shame they charge so much.

godelski 1y ago

Maybe I'm misunderstanding your request but do you not pipe outputs into a pager? (Less, more, batcat, etc) I feel like I'm probably not understanding the context though.

ec109685 1y ago
Sometimes you just have a command write output.
- rorytbyrne 1y ago
  In that case are scroll bars even helpful for determining position? My terminal history is normally huge, and the log output would be some unknown percentage of the total scrollable history.
- godelski 1y ago
  I'm still not quite sure what you mean. You can still {|,>} output from a program, so less and grep still help. Or do you mean when you inevitably forget? Well then yeah you're at the mercy of your terminal but as others mentioned ghostty has a hack to help as well as some other terminals. But this should also help reinforce why you should pipe more often and write to files (or tee). It sucks but not making the same mistakes in the future and learning better habits will help you write better code and use better practices. But that's the age old problem of "you can't analyze the data you didn't record" and that's a footgun you'll experience in every programming language, every experiment, and across many parts of life. Better to record and throw it away than not record and regret it.
  - horsawlarway 1y ago
    > "you can't analyze the data you didn't record" It IS recorded. It's right there in scrollback (Literally the default buffer to record). It's easily accessible with most tooling, including nice scrolling, mouse support, find/search, etc... Except in Ghostty, it's not so accessible. No find, no scrollbars. I end up having to dump it into another tool, which at least they make pretty easy (ex: https://ghostty.org/docs/config/keybind/reference#write_scrollback_file https://ghostty.org/docs/config/keybind/reference#write_scro...). Although deciding when to do that would be easier if I had a better indicator for just how much scrollback content exists. Ex - if it's 3 pages... I'll just scroll through it. If it's 3000 pages... time to dump to file. So no - by default I use a pager... just about never. Why would I when I have absolutely everything in scrollback by default 99.9% of the time? --- Don't confuse your preferences with "correct" :P I'm doing just fine with code and best practices, I'm simply stating that this is a rough edge on an otherwise lovely tool.