3 ms·
I haven't talked at all about whether incremental WYSIWYG editing of TeX documents is desirable, nor indeed about incremental WYSIWYG editing of TeX documents a
by kragen 4y ago
I haven't talked at all about whether incremental WYSIWYG editing of TeX documents is desirable, nor indeed about incremental WYSIWYG editing of TeX documents at all. Nor did I talk about whether a more responsive TeX workflow was desirable. The only things I said were desirable were (a) being less aggressive and (b) understanding the distinction between interpreters and compilers.
I have no idea why you would believe I agree with you about these objectives. Perhaps you have me confused with somebody else, in addition to being confused about what a compiler is, and about whether TeX has an interactive mode with a prompt, which it does (as, you point out, do many other interpreters).
Your proposed definition of "compiler", which would make grep a "compiler", as well as CPython when run with a .py file as an argument, but not HotSpot, is almost completely unrelated to the standard definitions. I have quoted a selection of them for your edification in https://news.ycombinator.com/item?id=32362579 https://news.ycombinator.com/item?id=32362579. The standard term for what you are calling a "compiler" is "batch-mode program".
- deleted 4y ago[deleted]
- Shorel 4y ago> I haven't talked at all about whether incremental WYSIWYG editing of TeX documents is desirable, nor indeed about incremental WYSIWYG editing of TeX documents at all. Nor did I talk about whether a more responsive TeX workflow was desirable. In that case, I find this conversation irrelevant to me. The precise definitions are just that, definitions, and are there to serve an objective, they are not the end themselves. Goodbye.