Don't scroll back down on ctrl-shift-M

[cool-RR]

Here's something that happens to me 10 times a day. I scroll way up using Ctrl-Shift-PgUp. I find some text I want to copy. I press Ctrl-Shift-M and bam! The shell scrolls me back all the way down to the bottom and turns on select mode. Now I gotta scroll all the way back. It really should stay exactly where it is.

[madhavansingh]

Hi, I wanted to add my experience with this issue for Hacktoberfest 2025.

Mac workflow / external keyboard scenario:

• Scroll up in the terminal using Ctrl+Shift+PgUp.
• Press Ctrl+Shift-M to enter select mode.
• The terminal jumps to the bottom and enters select mode, losing the scrollback position.

Expected Behavior:

• Select mode should activate without changing the scroll position.
• Users should remain exactly where they are in the scrollback buffer.

Impact:

• Disrupts copy-paste workflows when reviewing older output.
• Happens frequently during normal terminal usage (10+ times per day for me).

Workarounds (temporary):

• Use mouse selection (Shift + drag).
• Remap Ctrl+Shift-M to another keybinding in settings.

Additional Notes:

• I experience this on macOS using an external keyboard.
• Fixing this would improve workflow for users across different platforms.

Thanks!

[carlos-zamora]

Thanks for filing! A little bit of background. By design, if a selection already exists, when you enter mark mode, you start at that position. From your bug report, it sounds like you're scrolling up, then entering mark mode. Since there isn't an existing selection, Terminal will scroll you back to the bottom to where the cursor is.

A workaround would be to scroll up, then make a selection with the mouse. That way, you can edit it in mark mode.

That said, that kinda defeats the point! When you enter mark mode, you want the viewport to stay in the same spot and a selection to be created. The question is, where do you expect the selection to be created within the viewport /? Any suggestions? The fix itself should be pretty easy if we can get consensus on that.

[cool-RR]

A workaround would be to scroll up, then make a selection with the mouse

A better explanation to why this defeats the point is that If I wanted to use the mouse, I wouldn't even need Ctrl-Shift-M.

I'm happy you're on board with this feature request.

the question is, where do you expect the selection to be created within the viewport /? Any suggestions? The fix itself should be pretty easy if we can get consensus on that.

I would be fine with anything from the first character to last one to a random character in between. These will all be better than the current state. But the reasonable choice would probably be the first character.