-
Notifications
You must be signed in to change notification settings - Fork 377
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
🚀 Expose max_buffered_lines
as configurable option
#427
Comments
Hi @huzecong, thanks! I've done that in a branch named |
This is awesome, thanks for the speedy change! Here's an example diff that exhibits the problem; basically, any diff with > 32 consecutive lines of edits would trigger this:
I can confirm that the PR solves the problem. I was able to get normal output with the above diff when run with |
Great, that's merged to master. Thanks for the diff, a unit test for this shall be made out of it. |
Thanks for writing this wonderful piece of software! Here's my feature request:
Would it be possible to expose
max_buffered_lines
as a configurable option (preferrably as a command line argument)?Sometimes I need to work with large diffs using side-by-side mode, but when there are too many consecutive lines with diffs, it would get rendered as deleting and inserting whole lines instead of inline edits. Currently
max_buffered_lines
is hard-coded as 32, I could be wrong, but I don't see any reason that we couldn't set it to a larger number.The text was updated successfully, but these errors were encountered: