-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Duplicate Line pushes viewport down on long files #21
Comments
Hey Davey! |
@DaveyUS I think I've found a solution. Now, it will try scrolling the copied line into the middle of the screen (if there are enough lines above it). |
Thank you very much @SkepticMystic for mention me :) I'm feeling extremely comfortable with this new feature! I tested the many scenarios that I know in a long note as @DaveyUS mentioned:
In my humble opinion, 100% working on those scenarios:
Let wait the see @DaveyUS feedback :) Let me know if you new any different test @SkepticMystic :) I wish you guys a fantastic day! |
@FelipeRearden thank you so much for testing so rigorously! |
It's definitely better in the new update! I'm still getting jumps, but it's much less extreme. The goal is to get it to VS Code level where it doesn't jump ever, but I'm guessing you're forced to implement this in hacky kind of way so that might not be doable? Either way this works and saves me clicks so I'm grateful! |
I think my current approach is actually doing what VS Code does, just with alot less leniency for when to scroll the view. |
Just to let you guys know that version
Good luck 🍀 ! |
Great addition! I've been holding out for VS Code functionality for some time.
On long documents that extend past the bottom of the viewport, if you use your new duplicate shortcuts on a line near the top of the doc, it will jump the view to the bottom of the doc, which is of course pretty jarring. It works as it should otherwise, but you have to scroll all the way up every time you duplicate.
Forgive me if this is some problem with all of my custom CSS or something.
Thanks for doing what you do!
The text was updated successfully, but these errors were encountered: