[sargstuff]

Note how things are grouped / structured in emacs. (beyond the tree, aka implied surrounding environment, current abstraction level, abstraction level(s) below current abstraction level.

lisp (.) notation works for nice compact level notation aka outside (.) is parent environment, inside (.) is various levels of () abstraction, evaluating pair of () gives result of the () application evaluated. Where something like the bash shell, the (.) is what happens in the shell file, outside of the (.) is the command line environment, and inside () may be multiple nested shell file abstraction/other shell file references. Note: can extend the (.) concept to spreadsheets, where each cell in spread sheet is shell file & spreadsheet is "file directory".

Could check out how treesitter is used in vim/neovim vs. emacs. and/or 70's tex & nroff put together things.

ed fairly barebones editor, one step up from command line sed.

Slightly more modern approach, search engine term 'text editor written in ' adding language of choice/familiar with after 'in' aka 'text editor writtin in bash'. play around with source code.

[sargstuff]

What's the ide & code repository (with reports/code/"goals"/dev communication) being used? aka developer environment should take care of lot of non-code/code details that are needed for development, but not what the current developement focus is. aka focus using X11 for front end to database (vs. developing X11 gui library to use as front end).

lisp short notation, where in the (.) is the focus?

outside (.), result of some (.) nested in several (.) levels, or result of top (), or totally different top level ()?