-
Notifications
You must be signed in to change notification settings - Fork 5
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
Regarding the version #9
Comments
As you noted, I've just finished implementing some build/CI tooling improvements (over several repositories). I hadn't followed the upstream changes for a while since, for me, with v563, it has settled into a stable fully-usable form. But I'm happy to merge the changes when I get some more time to look at them. |
@rivy Thanks for looking into it. And, apparently 608 just came out 5 days ago. If it's helpful, I've compiled the release notes of the changes since 563, maybe you'll find something you like: v563 → v581: Change ESC-u command to toggle, not disable, highlighting per man page. FixesFix crash when using the @ search modifier. v581.2 → v590: Make less able to read lesskey source files (deprecating lesskey). FixesFix bug which could leave terminal in mouse-reporting mode after exiting less. v590 → v608: Add the --header option. FixesFix display of multibyte and double-width chars in prompt. |
Personally speaking, --redraw-on-quit would be particularly helpful for me, and I do like the new color options. |
I hope you can find time to work on this again. Here's the latest set of changes from the newest release (and helpfully they link to GitHub issues now): v608 → v633: Add LESSUTFCHARDEF environment variable (github #275). FixesFix incorrect handling of some Private Use Unicode characters. |
Now that the x.dev branch seems to be in full working order, will the version of less that you're using change, or is there a particular reason to go with version 563 in particular?
Current stable is 590 and the current beta is 608.
The text was updated successfully, but these errors were encountered: