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.

Sign up for GitHub

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

Jump to bottom

To cycle or not to cycle? #4

Open

LFDM opened this issue Feb 15, 2014 · 1 comment

Owner

LFDM commented Feb 15, 2014

Not sure if it's better to cycle when there is no next thing. or just throw the error, but catch with re-entering the submode we just were in.

Currently thinking cycling is better.

joeytwiddle commented Jul 30, 2014

Perhaps you can do like wrapscan which cycles but also displays a warning message, so the user is aware.

Also like wrapscan, you could make the behaviour optional, so users can choose if they want cycling or not.

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