From: Alexander Dahl <post@lespocky.de>
To: buildroot@busybox.net
Subject: [Buildroot] Is there a better version of vi?
Date: Thu, 3 Jun 2021 15:53:20 +0200 [thread overview]
Message-ID: <20210603135319.rfppvgyaezkvnkf5@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <f7452a41879246d3a3bdbe185657ccdc@AcuMS.aculab.com>
Hello David,
On Thu, Jun 03, 2021 at 01:27:56PM +0000, David Laight wrote:
> The version of vi is busybox is somewhat cutdown.
> I can't see an option to include either nvi or vim.
>
> 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.
Someone improved the Vi included in busybox lately, lots of changes
have gone to busybox master branch in the last months. Maybe you
could give that a try?
> Most annoying is not having :g//p
Not sure if that is covered.
Greets
Alex
--
/"\ ASCII RIBBON | ?With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.?
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20210603/b91eedb2/attachment.asc>
next prev parent reply other threads:[~2021-06-03 13:53 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 [this message]
2021-06-03 14:01 ` David Laight
2021-06-07 19:16 ` Arnout Vandecappelle
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=20210603135319.rfppvgyaezkvnkf5@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--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.