Conemu: Disable scrolling past lowest line

[bquistorff]

When scrolling down it would be nice if it stopped at the lowest line (rather than allowing scrolling past this into blank space) as is the behavior in putty and Cygwin. I couldn't find an option for this.

[Maximus5]

There is no "lowest line" term defined in Windows. Even if the cursor was left on some line, console applications may write below it using standard WinApi.
More cons than pros.
Will not implement that.

[pyhedgehog]

Maybe writing N empty lines on shell startup (in something like .bashrc) will help you?
Unfortunately there are no correct way to get "DefaultBufferHeight" option (GetOption macro is awful).

[Maximus5]

There is an example for cmd:
http://conemu.github.io/en/PromptAtTheBottom.html

[Ehekatl]

this is a very annoying feature...
resizing a window will lose focus on current output
really hope you could consider stop it somewhere, and when scrolling large output, it's easy to get lost.

[erikjasiak]

I'm adding a +1 even if this is "closed" ; any sort of scroll up referral to terminal history makes the terminal useless:
Either you overshoot the cursor, start typing, and lose everything above it
Or you waste an inordinate amount of time repositioning your window.

Please reconsider - even typing "conemu sto" into google autocompletes to "conemu stop scrolling" at this point.

[tcoulter]

Another :+1: as well. Conemu is the best Windows console I can find, and it's still very hard to have a pleasant developer experience.

[GeneriGithub]

Scrolling into empty space after the last line is really annoying. Any fix?

[CodeBrotha]

Is there a fix for this? Always overshooting the last line and having to scroll back to the exact position of the cursor is really annoying and slows me down.

[Maximus5]

Update and read whats new (Dynamic scrollbar range).
There is even the hotkey to position your buffer at the line with the cursor.

[tobia]

Wait, there's something I still don't understand.

ConEmu is clearly able to detect the range of buffer that has actually been filled, otherwise Dynamic scrollbar range wouldn't work. So why can't it lock the regular touchpad or mouse wheel scrolling to that range? What's the purpose of allowing the screen to fly below the range that has any actual text in it?

To put it another way: if I grab the scrollback handle, I'm limited to the correct range. If I want to scroll past that, for whatever obscure reason, I can always click on the arrow button at the end of the scrollbar.

Would it be possible to restrict the WheelDown and WheelUp events to the same "dynamic" range? Can we do it using a macro?

By the way, I'm already using the macros Scroll(0,1) and Scroll(0,-1) on WheelDown and WheelUp, because the default scrolling speed is way too high for a touchpad. If I could, I would reduce it even more, but Scroll() doesn't accept a float argument.