Date: Thu, 24 Mar 2011 01:16:32 -0500 From: Zhihao Yuan <lichray@gmail.com> To: Pan Tsu <inyaoo@gmail.com> Cc: freebsd-hackers@freebsd.org, Arnaud Lacombe <lacombar@gmail.com> Subject: Re: [GSoC] About the idea: Unicode support in vi Message-ID: <AANLkTim3hHctSJCqAu3fEpWuKXdv60Lt3pKrAiUeTBYs@mail.gmail.com> In-Reply-To: <86k4fpb2oi.fsf@gmail.com> References: <AANLkTintkKzW=o%2B7Q53aMSpA1mmqC7aDF1wN8zHY_Wc%2B@mail.gmail.com> <86mxkm1erm.fsf@gmail.com> <AANLkTin3Wki6bnriNgWUy5JC68MDMVc4Y444tGWcKBQ7@mail.gmail.com> <86aaglx1ow.fsf@gmail.com> <AANLkTikLbU--J2aVa00tzxWb9GAvjfGnUGovwYaXXqhp@mail.gmail.com> <AANLkTimKzTrLA%2BW4a73D=aS8fy9npeqvrS8Ua3oNKrjf@mail.gmail.com> <AANLkTin=Y-z-Rt0cnd3MRg0JoSWJmhC3Uh2b32Bosgfi@mail.gmail.com> <AANLkTimDnA6jdj-MR7J2EGAQFn=%2BRrS9h32N5UWkaDUs@mail.gmail.com> <AANLkTinuQG2ew4R81861Ei7Czds0pGVFaD4ExheFpnnE@mail.gmail.com> <86k4fpb2oi.fsf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 23, 2011 at 10:46 PM, Pan Tsu <inyaoo@gmail.com> wrote: > Zhihao Yuan <lichray@gmail.com> writes: > >> If you really want to use vi in a 32MB mem environment, the ex-vi may >> make sense. It consumes 1600KB memory while nvi consumes 2000KB. Note >> that the ee editor uses same amount memory as ex-vi. > > ex-vi memory usage can be reduced a bit, e.g. by ~20% if you drop > =C2=A0-DLISPCODE -DCHDIR -DFASTTAG -DUCVISUAL -DMB -DBIT8 > in particular multibyte support. > >> So basically, if no one disagree that we can drop the infinite undo, >> multiple buffer, multiple window and some other potential missing >> features, we can replace the nvi in the base system with ex-vi. > > If the intent is to make all interactive editors in base unicode aware > then I wonder if you can use similar excuse when window(1) was kicked > out but for missing features, i.e. use ports. If user accepts the window or even screen in ports, they can also accept ex-vi staying in ports. > > As for other editors, ed(1) seems to support editing UTF-8. I've used it > to read/edit cyrillic and CJK texts in single user mode before found out > about ex-vi. And ee(1)... why not add unicode support there as a GSoC? > ed seems works, but it's not either vi or ex. I'm not typically like ee... I sill wondering why we kept it in base system. It does not work when termcap is not correct, so I still need to use ed in such a case. Same thing happens to ex-vi. --=20 Zhihao Yuan The best way to predict the future is to invent it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim3hHctSJCqAu3fEpWuKXdv60Lt3pKrAiUeTBYs>