luxferre/nne
1
0
Fork 0
Code Actions Activity

Updated readme

Browse Source
This commit is contained in:
luxferre
2023-07-28 08:18:03 +03:00
parent 3f4d3e5f15
commit 1aeace39f0
2 changed files with 15 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+1 -5
View File
@@ -62,7 +62,7 @@ You get the idea.
Currently, nne can't be compiled with [TCC](https://bellard.org/tcc/) and [lacc](https://github.com/larmel/lacc) because they both fail with `undefined reference to '__dso_handle'` error. This symbol is used by the `atexit()` call that sets up the handler to clean up the terminal environment on any abnormal exit. For TCC, the error can be mitigated by directly linking with the `libc.a` from musl (as shown above) but the resulting binary still is dynamically linked with glibc and displays unstable behavior.
Also, [neatcc](https://github.com/aligrudi/neatcc) (+ [neatlibc](https://github.com/aligrudi/neatlibc)) can't compile nne because it lacks support for variadic macros.
Also, [neatcc](https://github.com/aligrudi/neatcc) (+ [neatlibc](https://github.com/aligrudi/neatlibc)) can't compile nne because it gives `strlen undefined` error.
## Usage
@@ -147,10 +147,6 @@ No. All the focus is going to be on fixing bugs (if there are any found) and siz
It should not be hard. Most (if not all) changes are going to be related to terminal I/O.
### Is there any refactoring planned to get rid of the variadic macro requirement?
Not in the foreseeable future. It would be nice to make nne buildable on more compilers, but it also might be wise to wait until small compilers such as neatcc start supporting such features.
### Why does `mod e` (running external command) force saving the currently edited file?
Because it can't guarantee that the external command won't kill the nne process itself. Thus, saving is enforced to preserve your data. Also, this shell runner feature is introduced for easy offloading of some functionality to external tools designed to do it much better than any in-editor features would allow, e.g. running `sed` to perform a global substitution on the very file we're editing right now. It would be a shame if this global substitution had been performed on an old copy of the file and any subsequent save had obliterated all the changes made by the external command.