From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Is there a better version of vi?
Date: Mon, 7 Jun 2021 21:16:49 +0200 [thread overview]
Message-ID: <df983b32-db5a-1eda-cee5-0b15c181a32c@mind.be> (raw)
In-Reply-To: <f7452a41879246d3a3bdbe185657ccdc@AcuMS.aculab.com>
On 03/06/2021 15:27, David Laight wrote:
> The version of vi is busybox is somewhat cutdown.
> I can't see an option to include either nvi or vim.
Symbol: BR2_PACKAGE_VIM [=n]
Type : bool
Prompt: vim
Location:
-> Target packages
(1) -> Text editors and viewers
Defined at package/vim/Config.in:1
Depends on: BR2_USE_MMU [=y] && BR2_USE_WCHAR [=y] &&
BR2_PACKAGE_BUSYBOX_SHOW_OTHERS [=y]
Selects: BR2_PACKAGE_NCURSES [=n]
I suspect you didn't turn on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
vim is pretty large though, adding nvi might be a good idea. Feel free to send
a patch!
Regards,
Arnout
>
> While vim has grown all sorts of horrid extensions
> it would be nice to have a version that matches the
> code from the late 1980s.
> Most annoying is not having :g//p
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
next prev parent reply other threads:[~2021-06-07 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 13:27 [Buildroot] Is there a better version of vi? David Laight
2021-06-03 13:53 ` Alexander Dahl
2021-06-03 14:01 ` David Laight
2021-06-07 19:16 ` Arnout Vandecappelle [this message]
2021-06-08 8:16 ` David Laight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df983b32-db5a-1eda-cee5-0b15c181a32c@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.