On Wed, Dec 20, 2017 at 07:53:31PM +0100, Klemens Nanni wrote: > On Mon, Dec 11, 2017 at 01:18:24PM +0100, Klemens Nanni wrote: > > On Sun, Dec 10, 2017 at 08:11:56PM -0500, Brian Callahan wrote: > > > This is not some famous piece of software like the GNU coreutils, where > > > accidentally using the base utility vs. the GNU utility could really > > > matter. > > Fair enough, I'm happy with a simpler port. > > > > > They bleed into each other. > > > When I load vis by itself, I get: > > > 0% 1, 1 > > > When I press i to enter insert mode, it becomes: > > > 0% 1, 1 1 > > > Then if I type, say, "OpenBSD" it shows: > > > 100% 1, 1 71 > > > Let's say I finish the sentence and now I wrote "OpenBSD is an operating > > > system." it will display: > > > 100% 1, 10311 > > > Now let's say I press Enter to move to the next line, it says: > > > 97% 2, 0311 > > > > > > I would say this is very broken. This is within tmux, which limited > > > testing > > > suggests makes a difference, but there are still bleeding issues when not > > > in > > > tmux. Specifically, outside of tmux, pressing i in a blank file still > > > produces > > > 0% 1, 1 1 > > I cannot reproduce this at all, whether in tmux or not. vis works fine > > for me in both xterm and st. > Brian is still the only I heard of having this issue, can anyone else > reproduce this?
I've been using vis a bit over the past week and the port seems to work just fine. In particular, I was unable to see the problems bcallah described. > Besides that, I renamed both binary and manual page to vise again to > avoid conflicts; conflicts should be avoided even if it might be of such > minor concern. > > Can anyone else please test this? If no further breakage comes up I'd > really like to see this port go in. If bcallah no longer objects, I'm ok with importing this version of the port. > > New tarball attached.
