How can I set up iTerm2 so that it auto-scrolls down even after I scroll up manually?
See GIF below. It starts scrolling down normally, but stops after I manually scroll up, even that output is still coming to stdout.
Changing this would help me a lot running jest tests in watch mode.
Related
I am getting a grey/white overlay when using commands that take up the entire terminal like nmon and bmon. The first image is iterm2 and the second is the base macos terminal app, both running nmon.
It is not the transparency settings as I have already disabled those, not sure what setting to change to fix this.
I'm running into this strange issue with my tmux in iterm where it appears to be rendering on the wrong line, but this causes strange rendering issues to happen
Here is the basic behavior:
You'll notice the menubar is offset by one line. This is fine, for the most part, except when I start entering tmux commands I get behavior like this:
I've also noticed that sometimes the menu bar will entirely disappear and I won't be able to show which sessions i have open. I've also noticed that sometimes if I select the text in my terminal with my mouse, it will select text one-line up from what I expected to select.
I've tried a bunch of things to debug this, including:
re-install tmux
clear tmux-resurrect history
restart my computer
reinstall iterm
resizing the iterm window (both manually, and using cmd+ and cmd, which I have a theory was what triggered this behavior)
I've also noticed that if I run tmux in the default terminal macOS application it behaves normally with no issues.
Does anyone have any ideas of things I could try?
I have unchecked all of these options, and the strange behavior disappears.
The scroll bar in WSL is not usable while running a process. My attempts to scroll up are futile because the system automatically sets the scroll bar to the bottom of the window since there's a process running.
In my case, I invoked ./gradlew bootRun, which starts an application on 8080 and keeps printing logs. I tried to read the logs by scrolling up but any manual upward movement of scroll bar was being overridden.
Just wondering if some other Windows 10 setting is causing this or is it specific to bash or is it specific to gradle? How to fix it?
I believe this is neither related to WSL nor to the shell, but to the terminal. And even in case of WSL the terminal is still conhost, which is also used by the regular Windows cmd prompt.
That said, I don't believe there's a fix / setting for this right now, but you might have luck seeing this address in the new terminal app being created currently by Microsoft. In its current state, though, I also see it auto-scrolling to the bottom for ongoing output.
I am using Firefox (Developer Edition) as my primary debugging environment for web-development. Is there any way to make the Web Console automatically scroll to keep up with new output as it is logged?
I am using Webpack with hot-module-reloading that the Web Console quickly fills up with messages. If it could automatically scroll, I would not need to move the mouse across two wide-screen monitors just to scroll down ever time I save code or HTML changes -- eyes move quicker than the mouse.
I've got tmux to scroll up, with the mouse wheel, using mouse-mode on in tmux.conf (here's my entire conf).
But I've always had a problem scrolling back down again. Once the cursor hits the bottom of the screen, it immediately scrolls back to the bottom of the whole buffer, where the prompt is. It's not possible to scroll down a few lines in the same way I can scroll up a few lines. In other words, the whole middle section is only visible on the way up.
I just upgraded from tmux 1.6 to the new tmux 1.8 (compiled from source rather than Homebrew, in case that matters), and it's working again now.
What would happen if you turned mousemode off and used the keyboard? Try that.
Have you used burningTyger's settings for your conf?
Try deleting the buffer command, maybe then it won't autoscroll to the prompt line. If you can disable any automatic behavior you might be able to do what you need.
I don't know the OSX terms, but hopefully these concepts might be helpful.