https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #13 from Michael ---
> This indicates that the command vi was actually calling vim. So the previous
> comments about vim behavior applies -- you were actually using vim when you
> thought you were using vi by the vi command.
ok, I see, you
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #12 from fanzhuyi...@gmail.com ---
(In reply to Michael from comment #11)
> on Linux
> VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Oct 16 2023 18:15:38)
> Included patches: 1-579, 1969, 580-1854, 1857, 1855-1857, 1331, 1858,
> 1858-1859, 18
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #11 from Michael ---
(In reply to fanzhuyifan from comment #9)
> On both konsole where you were witnessing this issue, and a terminal where
> you did not witness this issue, could you provide
>
> 1. The output of `vi --version`, if vi was t
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #10 from Michael ---
(In reply to ninjalj from comment #8)
> As already written in comment 3, it _is_ a vim behavior. See the description
> at https://vimhelp.org/intro.txt.html#window-contents
>
> If it doesn't show up in other terminals,
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #9 from fanzhuyi...@gmail.com ---
(In reply to Michael from comment #7)
> not a bug?
>
> what is it then?
If you insist, could you provide the following so that we could better debug
this issue?
On both konsole where you were witnessing th
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #8 from ninj...@gmail.com ---
As already written in comment 3, it _is_ a vim behavior. See the description at
https://vimhelp.org/intro.txt.html#window-contents
If it doesn't show up in other terminals, it's probably because they have
differ
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #7 from Michael ---
not a bug?
what is it then?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #6 from Michael ---
(In reply to fanzhuyifan from comment #5)
> (In reply to Michael from comment #4)
> Maybe you accidentally have an alias from vi to vim? Or you changed your
> config files? This does seem like expected vim behavior, as m
https://bugs.kde.org/show_bug.cgi?id=477078
fanzhuyi...@gmail.com changed:
What|Removed |Added
Resolution|--- |NOT A BUG
CC|
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #4 from Michael ---
(In reply to ninjalj from comment #3)
> That's a vim behavior. See
> https://vi.stackexchange.com/questions/102/show-partially-hidden-wrapped-
> lines and https://vimhelp.org/options.txt.html#%27display%27
well, I use vi
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #3 from ninj...@gmail.com ---
That's a vim behavior. See
https://vi.stackexchange.com/questions/102/show-partially-hidden-wrapped-lines
and https://vimhelp.org/options.txt.html#%27display%27
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=477078
--- Comment #2 from Michael ---
(In reply to ninjalj from comment #1)
> Can you provide detailed instructions on how to reproduce the problem?
sure,
take any text file, insert in the middle a line with 1000 words or so, save it
and scroll in vi
when
https://bugs.kde.org/show_bug.cgi?id=477078
ninj...@gmail.com changed:
What|Removed |Added
CC||ninj...@gmail.com
--- Comment #1 from ninj..
https://bugs.kde.org/show_bug.cgi?id=477078
Nicolas Fella changed:
What|Removed |Added
Severity|critical|normal
CC|
14 matches
Mail list logo
