Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation: Consider a better name for "emulate scrolling in fullscreen buffers" && Add it to README #16

Open
NHDaly opened this issue Apr 10, 2016 · 5 comments

Comments

@NHDaly
Copy link
Owner

NHDaly commented Apr 10, 2016

From #15: @prevent-scroll-for-fullscreen-alternate-buffer now actually enables scroll for those buffers, by emulating it.

Find a better name for this option.

@NHDaly
Copy link
Owner Author

NHDaly commented Apr 10, 2016

My current best idea is @emulate-scroll-for-no-mouse-alternate-buffer.

@NHDaly NHDaly changed the title consider a better name for "emulate scrolling in fullscreen buffers" Documentation: Consider a better name for "emulate scrolling in fullscreen buffers" && Add it to README Apr 10, 2016
@giddie
Copy link
Contributor

giddie commented Apr 11, 2016

Sounds OK to me :) I wonder if it might be worth enabling it by default? I suspect that the majority of people installing the plugin will want scrolling to "just work" in tmux, rather than compatibility with old tmux versions. Not a big deal, though, since the README isn't long.

@NHDaly
Copy link
Owner Author

NHDaly commented Apr 18, 2016

I wonder if it might be worth enabling it by default?

Yeah, I agree. But up until now, the default options have all been set to emulate the pre-2.1 behavior.

I've been considering changing the defaults to just be the best/most natural behavior, but I don't want to break people's configurations... I'm not sure how to make that change?

@NHDaly
Copy link
Owner Author

NHDaly commented Apr 19, 2016

Fixed in 5e4c864.

@giddie
Copy link
Contributor

giddie commented Apr 19, 2016

I'm not sure most would consider it a break. If they've installed the plugin and left everything at default behaviour, it's probably because they're not too fussed about the behaviour, and if anything will probably be in for a pleasant surprise on upgrade. Those that specifically want compatibility with old tmux behaviour (do we know these people exist?) will probably be fussy enough that they'll notice the change immediately and refer to the README to modify their config.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants