Paul Zinn-Justin
Paul Zinn-Justin
reminds me of an old discussion in the mailing list: On Thursday, November 10, 2016 at 5:11:25 AM UTC-6, Paul Zinn-Justin wrote: I have some very naive questions about projective...
... but as I mentioned in chat, a better solution would be to motivate the package creators (or yourself) to define `texMath` for their types ...
> aarggh! @DanGrayson I need to fix this one too this morning... Sorry :-P
Sounds like a good idea. I'll think about it.
proof of concept: given this (where code is in verbatim) [notes.pdf](https://github.com/Macaulay2/M2/files/7634927/notes.pdf) the script (written in m2) outputs this: [notes-parsed.pdf](https://github.com/Macaulay2/M2/files/7634932/notes-parsed.pdf) is this what you had in mind?
working on it: https://github.com/pzinn/M2inTeX
oh, I just realize in the title it referred to M2-merge. I just wrote this from scratch, no relation to M2-merge.
@mahrud I've just realized something: there's no reliable way to match the input and the output of `capture`. for example, I can easily fool it by creating a multi-line input...
the problem is not at the level of `separateM2output`. it's later when one tries to identify the input and the output. try to insert in documentation something like ``` Text...
I agree that I intentionally messed up the indentation. It does seem that the clean solution would be to capture successive chunks, but maybe that's too complicated to implement, you...