You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, thank you for your suggestion! I remember considering it initially but discarding it later on because of spacing in the floating window: with new lines it becomes very hard to peek a glance at the various registers. This said, as you mentioned, we can make it an option that users can select.
These days I will be unable to make the changes, however you might yourself propose a merge request by just changing this function; in particular, replace this character with a new line. What I suspect we must be careful to test is that these newlines characters do not break the parsing whilst copy and pasting (after selecting from registers), so let us make sure the behaviour is still what we expect.
Regarding truncation of long lines this may be much more cumbersome because the way the content is being pasted from the floating window is by highlight + selection, therefore if the text itself is truncated the truncation will be copied (not the original text); of course one could work around it, but it will require a much bigger change in the codebase (not sure it is worth the pain).
Instead of outputting newlines like:
it might be nice to see something like:
If there are too many lines, truncate:
This would be a config option,
g:peekup_new_lines = "split"
.(On a similar note, it might be a good idea to truncate long lines anyways.)
The text was updated successfully, but these errors were encountered: