0:46:10nyef`trinque: OTP is "one-time programmable", EPROM is "erasable" PROM. These things do not go together.
0:46:40nyef`OTP is "PROM", not "EPROM", and very far from "EEPROM" or "FlashROM".
0:48:40nyef`(Okay, "PROM", "EPROM", "EEPROM", and "FlashROM" are not, technically, "ROM", since they can be written, but they aren't "RAM", either, because writing them can be a pain (although the pain tends to decrease as you move along the spectrum from PROM to FlashROM).)
0:58:21trinqueah, took that to mean "one time pad" in the cryptographic sense.
1:04:54nyef`Meh. Just apply the Caesar cypher thirteen times. d-:
3:33:02beachhttps://en.wikipedia.org/wiki/Emacs says the same thing.
3:34:56beachI recently learned that the first Emacs implementation written in Lisp was NOT Multics Emacs, but some Lisp Machine implementation of it (ZMacs?).
3:41:38nyef`This would also be the programming language with the COME FROM statement, and some variants include the "computed" COME FROM, and the multi-threaded version where multiple COME FROM statements that come from the same place is used to spawn threads.
7:23:06manny8888I have been looking for documentation on how mcclim interfaces with backends. I have found nothing save for 1 page in the manual, and obviously reading through the code.
7:28:07beachI so wish we could eliminate this markup-language conundrum so that we could start uniformizing the documentation. Not any time soon, I fear.
7:33:04beachSo your solution to the problem that we have too many markup languages and that, because of that, any particular choice is rejected by 90% of developers, is to suggest yet another markup language?