On Fri, Mar 25, 2011 at 1:39 PM, Zhihao Yuan lich...@gmail.com wrote:
On Fri, Mar 25, 2011 at 8:45 AM, Kurt Lidl l...@pix.net wrote:
On Fri, Mar 25, 2011 at 10:40:44AM +0100, Johan van Selst wrote:
Zhihao Yuan wrote:
Could you please eleborate on the nvi-devel problems? I'm the current
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
Among *all* the GNU/Linux distributions I used, they include a vim
compiled in
On Sat, Mar 26, 2011 at 3:45 AM, Paul Schenkeveld free...@psconsult.nl wrote:
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
On Sat, Mar 26, 2011 at 03:55:12AM -0500, Zhihao Yuan wrote:
On Sat, Mar 26, 2011 at 3:45 AM, Paul Schenkeveld free...@psconsult.nl
wrote:
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
I like the
Zhihao Yuan wrote:
Could you please eleborate on the nvi-devel problems? I'm the current
maintainer of this port, and as far as I know it's fully functional.
1. It does not support non-Unicode encodings. Actually, these
encodings are mainstream in multi-byte encodings world. A proper
On Fri, Mar 25, 2011 at 10:40:44AM +0100, Johan van Selst wrote:
Zhihao Yuan wrote:
Could you please eleborate on the nvi-devel problems? I'm the current
maintainer of this port, and as far as I know it's fully functional.
1. It does not support non-Unicode encodings. Actually, these
On Fri, Mar 25, 2011 at 8:45 AM, Kurt Lidl l...@pix.net wrote:
On Fri, Mar 25, 2011 at 10:40:44AM +0100, Johan van Selst wrote:
Zhihao Yuan wrote:
Could you please eleborate on the nvi-devel problems? I'm the current
maintainer of this port, and as far as I know it's fully functional.
1.
On Wed, Mar 23, 2011 at 10:46 PM, Pan Tsu iny...@gmail.com wrote:
Zhihao Yuan lich...@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
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
Among *all* the GNU/Linux distributions I used, they include a vim
compiled in
On Thu, Mar 24, 2011 at 6:11 AM, Bernd Walter ti...@cicely7.cicely.de wrote:
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
On Thu, Mar 24, 2011 at 06:49:24AM -0500, Zhihao Yuan wrote:
On Thu, Mar 24, 2011 at 6:11 AM, Bernd Walter ti...@cicely7.cicely.de wrote:
Let clean up the my points:
1. ex-vi is POSIX vi compatible, and it supports mbyte encodings. But
there are lots of work need to be done if we want to
Zhihao Yuan lich...@gmail.com wrote:
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.
History:
ee
On Thu, Mar 24, 2011 at 5:07 PM, Julian H. Stacey j...@berklix.com wrote:
Zhihao Yuan lich...@gmail.com wrote:
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
Zhihao Yuan wrote:
2. nvi does not use iconv, nvi-m17n only supports limited non-Unicode
mbyte encodings, nvi-devel has too many problems. So we don't have a
nvi which comes with fully mbyte enconding support;
Could you please eleborate on the nvi-devel problems? I'm the current
maintainer of
On Thu, Mar 24, 2011 at 5:17 PM, Johan van Selst joh...@stack.nl wrote:
Zhihao Yuan wrote:
2. nvi does not use iconv, nvi-m17n only supports limited non-Unicode
mbyte encodings, nvi-devel has too many problems. So we don't have a
nvi which comes with fully mbyte enconding support;
Could you
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal is slightly different:
I want to fork nvi and make it iconv-awared (or mbyte-mode tunable,
like tcsh), so that
On Wed, Mar 23, 2011 at 2:23 AM, Pan Tsu iny...@gmail.com wrote:
Zhihao Yuan lich...@gmail.com writes:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal
On Wed, Mar 23, 2011 at 12:39:44AM -0500, Zhihao Yuan wrote:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal is slightly different:
I want to fork nvi
On Wed, Mar 23, 2011 at 12:39:44AM -0500, Zhihao Yuan wrote:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal is slightly different:
I want to fork nvi
On Wed, Mar 23, 2011 at 12:39:44AM -0500, Zhihao Yuan wrote:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal is slightly different:
I want to fork nvi
Zhihao Yuan lich...@gmail.com writes:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal is slightly different:
I want to fork nvi and make it iconv-awared
Am 23.03.2011 10:13, schrieb Alexey Shuvaev:
On Wed, Mar 23, 2011 at 12:39:44AM -0500, Zhihao Yuan wrote:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm interested in the idea that to
improve the nvi in the base system. My proposal
On Wed, Mar 23, 2011 at 02:38:20PM +0100, Matthias Andree wrote:
Am 23.03.2011 10:13, schrieb Alexey Shuvaev:
On Wed, Mar 23, 2011 at 12:39:44AM -0500, Zhihao Yuan wrote:
Hi,
I'm a Computer Science student at Northern Illinois University, and I
used FreeBSD for a long time. I'm
Am 23.03.2011 16:06, schrieb Alexey Shuvaev:
Yes, nvi-devel is not developed any more, but I was saying that nvi
in base is even older than nvi-devel, and it is worth looking at
it. At least for the iconv support. As for the BDB, maybe strip it just
out, if possible?
I don't believe it's
Zhihao Yuan lich...@gmail.com writes:
Why not just use traditional vi?
http://ex-vi.sourceforge.net/ (lives under editors/2bsd-vi)
This one lacks of many feature, compared with nvi.
nvi also lacks some features, e.g. lisp, modelines, sourceany.
ex-vi is more lightweight
# both built
On Wed, Mar 23, 2011 at 11:05 AM, Pan Tsu iny...@gmail.com wrote:
Zhihao Yuan lich...@gmail.com writes:
Why not just use traditional vi?
http://ex-vi.sourceforge.net/ (lives under editors/2bsd-vi)
This one lacks of many feature, compared with nvi.
nvi also lacks some features, e.g.
Hi,
On Wed, Mar 23, 2011 at 4:36 PM, Zhihao Yuan lich...@gmail.com wrote:
On Wed, Mar 23, 2011 at 11:05 AM, Pan Tsu iny...@gmail.com wrote:
Zhihao Yuan lich...@gmail.com writes:
I'm not sure whether the FreeBSD system administrators (who opens 100
ssh sessions) agree with that to replace the
On Wed, Mar 23, 2011 at 4:50 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 4:36 PM, Zhihao Yuan lich...@gmail.com wrote:
On Wed, Mar 23, 2011 at 11:05 AM, Pan Tsu iny...@gmail.com wrote:
Zhihao Yuan lich...@gmail.com writes:
I'm not sure whether the FreeBSD system
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
Among *all* the GNU/Linux distributions I used, they include a vim
compiled in tiny mode (ln -s it to vi), which doubles the size of nvi,
in their base systems. A vim.tiny contains much more features compared
with nvi,
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
Among *all* the GNU/Linux distributions I used, they include a vim
compiled in tiny mode (ln -s it to vi), which doubles the size of nvi,
in
On Wed, Mar 23, 2011 at 08:20:07PM -0500, Zhihao Yuan wrote:
On Wed, Mar 23, 2011 at 7:26 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Wed, Mar 23, 2011 at 7:32 PM, Zhihao Yuan lich...@gmail.com wrote:
Among *all* the GNU/Linux distributions I used, they include a vim
compiled in
Zhihao Yuan lich...@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
32 matches
Mail list logo
