Cool. Compiled easily, made a binary that does look like a text editor, let me make new files and edit an existing one. Only linked against libc, about a thousand lines of C.
So yeah, that is indeed a working text editor that doesn't link against ncurses and the like. Smaller than I would have expected it to be.
Most of that is probably attributable to being based on Kilo: https://github.com/antirez/kilo - a tiny text editor written by antirez who notably also created Redis. Antirez has a bunch of really interesting side projects if you dig into their github repo.
they aren't part of whatever standard yet they are still pure C. Pure C is not a well defined term but it refers to the fact that only the C language was used for the project. Which C version and whether other libs have been used is not part of the term.
I'll not enter the pure-C vs. non-pure-C debate, but this heavily depends on a Unix-like OS and VT100-like terminal. Forget to compile it for Windows, for example.
Very nice project, well organized, with a terse style. Comments are missing but not necessary.
Now that hardware terminals are gone, it's a very safe bet.
But xterm is,way rich, it supports esoteric advanced stuff like sixels, etc. For a basic text editor, without split windows, colors, and such, a subset of VT-52 capabilities may suffice.
My guess would be it targets VT-100, but it wouldn't have to be hardcoded, non-curses applications can still make use of the terminfo database to determine the capabilities of whatever terminal they are attached to.
Like many I appreciated seeing Antirez's kilo project, and went my own direction with a trivial fork: adding support for an embedded lua scripting language, allowing multiple buffers, and flexible syntax highlighting for different languages, etc.
For me one of the challenges was getting UTF8 support, since I live in Finland and am exposed to ä, ö, and other characters. It was a fun learning experience, even though I never intended it to become a "real editor" and I continue to use emacs on a daily basis.
Quickly looking over the (closed) bug reports I see the discussion I had with myself back in 2016 which largely caused me to rewrite the core in C++ so I could take advantage of modern facilities to make UTF8 work more easily:
I think you're reading intent that isn't there with this project. The author states its a WIP, and is writing it as a learning experience for building text interfaces without ncurses.
[+] [-] JonChesterfield|2 years ago|reply
So yeah, that is indeed a working text editor that doesn't link against ncurses and the like. Smaller than I would have expected it to be.
[+] [-] kamranjon|2 years ago|reply
[+] [-] linhns|2 years ago|reply
[+] [-] gdevenyi|2 years ago|reply
https://micro-editor.github.io/
[+] [-] rahen|2 years ago|reply
[+] [-] pjmlp|2 years ago|reply
Pure UNIX/POSIX C, more likely.
[+] [-] djur|2 years ago|reply
[+] [-] halayli|2 years ago|reply
[+] [-] teo_zero|2 years ago|reply
Very nice project, well organized, with a terse style. Comments are missing but not necessary.
[+] [-] Underphil|2 years ago|reply
[+] [-] mise_en_place|2 years ago|reply
[+] [-] schemescape|2 years ago|reply
I thought something like that must exist, but I haven’t found it yet…
[+] [-] Aloha|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]
[+] [-] WesolyKubeczek|2 years ago|reply
[+] [-] nine_k|2 years ago|reply
But xterm is,way rich, it supports esoteric advanced stuff like sixels, etc. For a basic text editor, without split windows, colors, and such, a subset of VT-52 capabilities may suffice.
[+] [-] MobiusHorizons|2 years ago|reply
[+] [-] 6R1M0R4CL3|2 years ago|reply
[+] [-] mogoh|2 years ago|reply
[+] [-] queuebert|2 years ago|reply
[+] [-] tyingq|2 years ago|reply
[+] [-] nittanymount|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]
[+] [-] tekla|2 years ago|reply
[+] [-] nox100|2 years ago|reply
[deleted]
[+] [-] stevekemp|2 years ago|reply
For me one of the challenges was getting UTF8 support, since I live in Finland and am exposed to ä, ö, and other characters. It was a fun learning experience, even though I never intended it to become a "real editor" and I continue to use emacs on a daily basis.
Quickly looking over the (closed) bug reports I see the discussion I had with myself back in 2016 which largely caused me to rewrite the core in C++ so I could take advantage of modern facilities to make UTF8 work more easily:
https://github.com/skx/kilua/issues/49
[+] [-] pharrington|2 years ago|reply
[+] [-] JonChesterfield|2 years ago|reply