vim-live-server

depends on a few things: a) what language(s) the editor is written in -- compiled (view source code or compiled code) vs. interpreted (view script(s) source code) b) support for utf8/utf16/utf32. c) shell command line based (sed/ed) vs. interpreted text editor program[4] vs. text application[2] ---- no, text editor would not hide anything from the user[1] (unlike wysiwig[2]) few ways to interpret what's being asked: text editor using treesitter extentions with approrpiate programming lanauge knowlege does allow for 'rolling up/down code blocks' to reduce/expand displayed code per lanauge groupings to reduce screen clutter. An ai can be used 'autobuild'/associate macros/tags references. where ai would translate/redirect 'verbal/audio' english commands to relevant text editor macros. This would be more akin to the human version of compute

several possible ways to interpret question asked: 1) openbox is a gui window manager. When run from a text console, a gui window manager provides access to graphical environment. ( additional example: Solaris NeWS window manger[10] ) xinit[9] is one aproach a user can use to customized which window manager to start/use. tmux[1], screen[2], byobu[3], wezterm[4] provide console 'text' equivalents (aka no graphics/graphics drivers) of gui window mangers such as openbox. 2) Examples of text editors that make use of features of the gui window manager the text editor is run under: gvim, gedit, leafpad[5], overleaf[6] 3) text editor with 'run-time' presentation extension of protocols such as html : vim live server[7] 4) write one's own custom interface to use with bashed[8] ---- [0] : intro to terminal multiplexers (part 1) : https://w

C++ isn't a text editor. Why would one want to use a non-lisp language within emacs? Zed[4] is fairly new. Swift as wrapper/unix io cli pipe feed around sed for interactive editing or pre/post process input/output to sed without the need to use/understand c++ just requires an understanding of unix cli, swift and just enough sed. Pretty easiy to add swift as an extension language to bashed[3]. Off the cuff guess: insufficient demand within main editor project for swift as language extension. Demand/use for supported extension languages within framework/ IDE / office suite (open office) does require significant/continuous time/effort to be supported within the main editor project. But why an extension language for text editor instead of using editor plugins / text transform dls? (where can insert call to swift program(s) to do transform wor

This is a simple but useful plugin that acts as a frontend to browser-sync and live-server from npm.