December 12, 2012 at 09:25Convenient development for OS Inferno in Vim
FAQ: What is OS Inferno and why is it needed?
You can write software for inferno both inside the inferno itself (using Acme IDE , the limbo and mk compiler for assembly), and outside, in host os (using any editor / IDE, and host os versions of limbo and mk) - while running inferno only needed to run tests or debugging. I have prepared several projects / scripts that are designed to simplify development for inferno in general, and development using Vim running in host os in particular.
Syntax highlighting for different file formats: limbo , sh , mk (mkfile) .If you already use highlighting for limbo - update the file, it has been rewritten and now fully supports the current limbo syntax.
The plugin for viewing documentation viewdoc now supports infernovye man-pages. For example, you can click
Plugin for checking syntax via Syntastic : limbo.vim (save to
for SnipMate (just as an example) : limbo.snippets (save to
inferno-opt-setup: scripts for "installing" (more precisely, bind) 3rd-party projects located in
inferno-opt-mkfiles : a set of mkfiles designed specifically to simplify the development of regular and / opt projects support building and testing the project both internally and host os, generating man pages from documentation in asciidoc format , etc.
inferno-opt-skel : an example project with an application, library, tests, documentation - for use as an example and a template for quick start of new projects.
inferno-contrib-tap: a library for limbo that makes it easy to write tests with output in TAP (Test Anything Protocol) format. When developing in host os using the mkfiles mentioned above, this allows you to run tests using the very convenient prove command (included in perl).
For everything to work, you need to set the environment variable
You can write software for inferno both inside the inferno itself (using Acme IDE , the limbo and mk compiler for assembly), and outside, in host os (using any editor / IDE, and host os versions of limbo and mk) - while running inferno only needed to run tests or debugging. I have prepared several projects / scripts that are designed to simplify development for inferno in general, and development using Vim running in host os in particular.
Syntax highlighting for different file formats: limbo , sh , mk (mkfile) .If you already use highlighting for limbo - update the file, it has been rewritten and now fully supports the current limbo syntax.
The plugin for viewing documentation viewdoc now supports infernovye man-pages. For example, you can click
deletein the source on limbo, and the documentation for the corresponding lists (2) module will be opened . Plugin for checking syntax via Syntastic : limbo.vim (save to
~/.vim/syntax_checkers/). Snippetsfor SnipMate (just as an example) : limbo.snippets (save to
~/.vim/snippets/). inferno-opt-setup: scripts for "installing" (more precisely, bind) 3rd-party projects located in
/opt. inferno-opt-mkfiles : a set of mkfiles designed specifically to simplify the development of regular and / opt projects support building and testing the project both internally and host os, generating man pages from documentation in asciidoc format , etc.
inferno-opt-skel : an example project with an application, library, tests, documentation - for use as an example and a template for quick start of new projects.
inferno-contrib-tap: a library for limbo that makes it easy to write tests with output in TAP (Test Anything Protocol) format. When developing in host os using the mkfiles mentioned above, this allows you to run tests using the very convenient prove command (included in perl).
For everything to work, you need to set the environment variable
$INFERNO_HOMEin the host os directory, which should be connected as your home directory inside inerno, and always call mk with the parameter in host os ROOT=/каталог/инферно- the easiest way is to ensure this by creating a script wrapper ~/bin/mk:#!/bin/bash
exec /usr/inferno/Linux/386/bin/mk "$@" ROOT=/usr/inferno