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
always show buffer content on start even if pattern specified via CLI matches nothing #135
Comments
Same with workarounds I discovered:
I still wish paint-before-message was default behavior. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: less 580
Currently, in case the search pattern is passed via the command line options, and if there's no match, like the case with the following command:
In this case, upon starting, less doesn't show the buffer content, namely
abc
in this case, instead it only displays the error message:It would be better that the buffer content is also made visible before the above error message is dismissed.
The text was updated successfully, but these errors were encountered: