@Pavel Does a "language" here don't need to be a "programming language"? (If so, I would request some trivial languages like HQ9+ and Hello in order to increase the language counter.)
@A_ It needs to not fit the PPCG definition of a language (Must be able to do addition and primality checking), must not be completely stupid (mostly stupid is ok)
There are several languages on TIO that I'm willing to bet haven't been used since a day after they were added
Even if just looking it up in a table was a valid solution (I don't think it is, and either way you can't put a bunch of files into the filesystem before execution on TIO), I don't see how you transfer a number from the editor's buffer to the ctrl-r input
@Pavel You type the number in a separate buffer, and then for the Ctrl-R, the command clears the other buffer and then reads a file to the main buffer.
@Pavel Right, we should add regex to TIO too.
I mean the regex that is in ed.
Hmm, does nano support regex?
nano seems to support regex, but I can't use it.
TIO already has too many text editors, and there is no need to add more.
In fact, the total of 655 languages is a waste of server space.
(What's the point of getting all this fame for a server with a pile of useless languages?)
<hr/>
@Pavel Why is Malbolge on TIO when nobody has written a prime-checking program?
Malbolge is programming language for finite automata, the same as *, and, for example, Befunge-93. Therefore Malbolge is formal programming language, the same as *, technically the same as recursively enumerable languages when it comes to programming language definition (albeit formal languages are less powerful). – Krzysztof Szewczyk
At least when I was testing it, vimscript is happy to read files in either latin1 or utf-8 with no difference in behavior (which is why the -u flag went away)
The environment variable LANG (which is reset by env -i) is read and interpreted by vim. Á is converted to 0xc3 0x81 when you enter it in your terminal emulator (set to UTF-8) or TIO (also set to UTF-8).
@DJMcMayhem How does the hexdump work? EOF (-1) is 0xFF when converted to a byte, and the Unicode character U+00FF is 0xC3 0xBF in UTF-8.
@Dennis The way I set it up was calling vim with the -w file flag (record keystrokes to a file), and then after the main vim had finished executing calling a secondary vim to open up the keystroke file and xxd it from within vim