Replies: 1 comment 3 replies
-
Forget it. Inline images are added via |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If
snacks.image
could add just one more feature, I think I’d never need to search for anothermarkdown
editor for the rest of my life! The plugin’s inline image preview is already fantastic.But there’s one small issue: whenever I move through the document using
j
ork
, if the cursor passes over an image element, the image suddenly appears and the document auto-scrolls to reveal the full image.This well-meaning auto-scroll behavior ends up conflicting with visual expectations and operational control—it completely breaks the immersive experience of editing.
It makes you feel like you’ve lost full control over Vim, because during normal editing, you’d never expect that pressing a single
j
key would cause the entire page to scroll half a screen and make familiar content suddenly disappear from view.I know the
float
preview mode avoids this kind of unexpected scrolling, but that’s not the effect I’m looking for either.What I really want is: in inline rendering mode, when scrolling with
j
andk
, image elements should also scroll “line by line.”Since we already have a configuration that maps image height to a certain number of “lines,” each press of
j
ork
should scroll by1/n
of the image’s height, rather than triggering the full image to appear all at once.This would prevent the sudden visual jump and align perfectly with the user’s mental expectation of scrolling behavior.
Additionally, it would be great to mark the current line position in the area where the editor normally displays line numbers and icons—on the left side of the image.
That way, users can visually track the cursor’s position even when navigating through image blocks.
Beta Was this translation helpful? Give feedback.
All reactions