Closed wilhelmy closed 4 years ago
The SDK and our RTL only support a subset of the printf variants. You are using ones that aren't and so are pulling in the newlib libc/stdio functions which use the newlib allocators rather than the SDK one.
BTW in-line editing is quite complex and command line history really too much of a luxury when you only have 44Kb RAM available.
The only printf-style function I call is snprintf. That's supported, right?
Regarding resource constraints, I'm aware. Input history is limited to 2k (4 lines at 512b). Linenoise is relatively lightweight and simple by cutting corners. I'd say it's probably the best option on embedded systems.
I don't think this really belongs into the issue tracker but I don't know what would be a more appropriate way to discuss it, sorry
The GitHub issue template links to http://nodemcu.readthedocs.io/en/dev/support/.
Yup until you prepare and frame this as a PR, then the best place for more informal discussion is on our Gitter channel.
I see. Thanks! Closing this then.
Linenoise input
Justification
Using an input library would make it easier to use the serial line interactively. I'm currently working on adding linenoise because it's small yet relatively full-featured and does not have too many dependencies on a POSIX environment compared to libedit and libreadline.
I would appreciate some help with the following linker problem (I don't think this really belongs into the issue tracker but I don't know what would be a more appropriate way to discuss it, sorry)