Can We Have At Least nvi?

[justledbetter]

BurmillaOS Version: (ros os version)
v1.9.1

Where are you running BurmillaOS? (docker-machine, AWS, GCE, baremetal, etc.)
hyper-v

Which processor architecture you are using?
x86_64

Do you use some extra hardware? (GPU, etc)?
no

Which console you use (default, ubuntu, centos, etc..)
default

Do you use some service(s) which are not enabled by default?
no

Have you installed some extra tools to console?
no

Do you use some other customizations?
no

Please share copy of your cloud-init (remember remove all sensitive data first)

rancher:
  console: default
  environment:
    EXTRA_CMDLINE: /init
  services_include:
    hyperv-vm-tools: true
  state:
    dev: LABEL=RANCHER_STATE
    wait: true
  upgrade:
    url: https://raw.githubusercontent.com/burmilla/releases/v1.9.x/releases.yml
ssh_authorized_keys:
- XXXX

For those of us who have been using unix long enough and can't do anything about our extreme muscle memory, can we at least have some form of minimalistic vi as a part of the default console? :)

I will add: I'm very thankful to you guys for forking ROS and continuing maintenance! After running ROS for four years in production, it's wonderful to not have to radically rethink my workflow just becase k3s is the trendy new thing. Please keep us all posted on how we can support the project and make sure this is a continued success for everyone!

[olljanat]

For those of us who have been using unix long enough and can't do anything about our extreme muscle memory, can we at least have some form of minimalistic vi as a part of the default console? :)

Good question. We decided switch default console to Debian on #9 and as part that I did switch from full vim to nano as that was smaller option. Nvi maybe would be better option but I'm not very eager to go back and forward with these.

@h8liu You was also missing some tools from current console?

I will add: I'm very thankful to you guys for forking ROS and continuing maintenance! After running ROS for four years in production, it's wonderful to not have to radically rethink my workflow just becase k3s is the trendy new thing. Please keep us all posted on how we can support the project and make sure this is a continued success for everyone!

We have long discussion on #88 about long term architecture. It would be nice to get more people testing and commenting those LinuxKit based examples I posted on those two last messages starting from: #88 (comment)

[olljanat]

Like discussed on #102 (comment) I think that it is better to leave v1.9.x as is even it is not optimal and fix this on v2.x versions as those are still on beta phase.

[justledbetter]

Very happy to have a vi type editor on the roadmap. Is there a branch you would like for me to try submitting a PR against? 😁

[olljanat]

Master branch

[justledbetter]

OK, I will get something tiny put together and see how it looks.

[justledbetter]

This change is merged into master, should be resolved in the next 2.x build.