I was thinking more about the installation/recuperation process than
the daily usage, because it's not always possible to install vim in
such cases. That's why I was questioning only vi being in [core],
though having vim in [core] would add lots of dependencies, so I guess
it's better the way it is. Especially if other distros are using the
same vi package, and still there is nano.
On Wed, May 6, 2009 at 8:07 AM, Jan de Groot <jan@xxxxxxxxxxxxxx> wrote:
> On Wed, 2009-05-06 at 07:54 -0300, André Ramaciotti wrote:
>> Hi,
>>
>> Just a question about this new vi package. Am I the only one having
>> problems when openning UTF-8 files? I can't even type words with
>> diacritics or vi will abort. For example, try to create a file with
>> the following and then open it with the new vi package:
>>
>> This line will render fine
>> Mas essa aqui não ("but this one won't" in Portuguese).
>>
>> I know that config files from Arch don't have diacritics, but I don't
>> think that putting this vi package in core will be a good idea.
>>
>> (The new vim package is working fine, though.)
>
> vi is just a bare editor which has its limits. One of them is not being
> able to use the cursor keys while you're in insert mode for example.
> This issue is known on many platforms: other linux distributions,
> FreeBSD, OpenBSD, etc. They all have nvi or some other vi clone in the
> base system.
> If you want support for non-ASCII charsets and other things offered by
> vim, just install vim.
>
>
