NxConsole is a related feature based on an NxTerm. It takes I/O from
/dev/console so provides an NSH shell on a framebuffer.
There are several screenshots of an NxConsole (running under the NxWM
window manager) here:
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=139629473&p
Sounds like you need an nxterm. An nxterm is the logical counterpart to
an xterm. You can find it at nutts/grapphics/nxterm.
It supports echoing text in a framebuffer and quite a few VT100 keyboard
inputs. There are all also lots of example to illustrate building and
using it. It hasn't be
Alan, I think that some honest discussion may be necessary regarding
rules propositions that are blocked only with your -1 vote and quite
against the discussion on breaking changes, thus allowing breaking
code to be freely merged with the upstream, with no breaking changes
handling process, and by
Hi Tomek,
My vote -1 was because the breaking text was saying that the author of
commit needs to test it and many (all?) arch and boards supported by NuttX.
This transfers the responsibility of NuttX QA from the project organization
to the end developer, that is unfair. We as project responsible