M.K.
- [x] This PR is for the `dev` branch rather than for `master`. - [x] This PR is compliant with the [other contributing guidelines](https://github.com/nodemcu/nodemcu-firmware/blob/dev/CONTRIBUTING.md) as well (if not, please describe...
### Missing feature Configurable independent startup delays for the startup task (typically init.lua), and the default UART interface (greeting + REPL). ### Justification When trying to share my output from...
### Missing feature An easy way to generate `app/include/user_*.h` from config presets that can inherit and override each other. At the very minimum, let's do that Debian priority config thingy...
### Missing feature Let's make the comments in `app/include/user_*.h` more machine-readable: * macro name * default value * category * importance level or sth. * short description * (optional) detailed...
### Expected behavior * `cd app/lua/luac_cross && make LUA=53 clean all` either builds a useful executable or refuses with a link to this issue to explain why we don't support...
### Expected behavior 1. SPIFFS is flashed to the user-specified location. 2. Files created by the Makefile have meaningful names. ### Actual behavior On branch "dev": 1. I don't know...
Summary of #1640. I extrapolated the reasoning to other transport layer packaging, hope it's the right conclusion.
Most style decisions are explained in the readme, but I couldn't find the reasoning on why a BOM is considered bad. Where I've looked: * [the patch](https://github.com/airbnb/javascript/commit/d9cb343b518349982f3b094f2ce48eda8347e6c7) that enabled it,...
Most command examples currently shown do the operation way worse than what I'd expect thunar would do (and afair, does). Here's an attempt at fixing the most obvious differences. ```diff...
Most GUIs (at least from big vendors) are built with some basic concepts of user happiness in mind: * warn about potential accidents. (`--interactive`) * confirm success. (`--verbose`) * documentation...