Hi hackers,
I'm doing my GSoC project, Multibyte Encoding Support in Nvi at
https://github.com/lichray/nvi2 . Currently, the editor can support
read/display/write multibyte encoding through iconv. Before adding
more features like file encoding detection, I want to remove some
features in nvi.
On Thu, Jul 14, 2011 at 01:22:49AM -0500, Zhihao Yuan wrote:
Hi hackers,
I'm doing my GSoC project, Multibyte Encoding Support in Nvi at
https://github.com/lichray/nvi2 . Currently, the editor can support
read/display/write multibyte encoding through iconv. Before adding
more features like
On Thu, Jul 14, 2011 at 01:22:49AM -0500, Zhihao Yuan wrote:
Second, the perl/tcl interpreter support; you can apply a perl/tcl
command to the file whiling you are editing. I beg no one here used
this feature before.
Bzzt. I've used the perl interpreter before on a project.
In that case, we
Both the guy and me failed to reply to the group. Let me forward it.
-- Forwarded message --
From: Zhihao Yuan lich...@gmail.com
Date: Thu, Jul 14, 2011 at 3:58 AM
Subject: Re: [GSoC]I want to remove everything perl/tcl/gtags in the new nvi
To: Sebastian Chmielewski
On 7/14/11 1:07 PM, Zhihao Yuan wrote:
I regards nvi as a trustful editor when you login into other ppl's
machines.
Yes - this is the exact use case for Vi in my mind. If I needed features
I'd install vim. Come to think of it, since there is already a vim-lite
and vim port, why not make a
On Thu, 14 Jul 2011 01:22:49 -0500
Zhihao Yuan lich...@gmail.com wrote:
Hi hackers,
I'm doing my GSoC project, Multibyte Encoding Support in Nvi at
https://github.com/lichray/nvi2 . Currently, the editor can support
read/display/write multibyte encoding through iconv. Before adding
more
Here is my introspection:
Q: Why drop DB3/4?
A: Licenses problem.
Q: Licenses problem matters?
A: It causes we can't accept nvi-1.8x in our base system.
Q: Why an editor in the base system?
A: Always accessible. Anywhere (SSH), any situation (inc. system crashes).
Q: Why not vim-lite/original-vi?
7 matches
Mail list logo