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

Introduce a `SAFE_RANGE` #1

Open

mmalecki opened this issue Apr 26, 2021 · 0 comments

Owner

mmalecki commented Apr 26, 2021

Currently, with custom commands, there's no way for the user to know what the safe range is.

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