[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #59546] Missing latex interpreter
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #59546] Missing latex interpreter |
Date: |
Fri, 27 Nov 2020 11:19:13 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36 |
Follow-up Comment #5, bug #59546 (project octave):
This sounds like a great addition to Octave. Also, I'm not particularly
bothered by speed (within reason). The core bits of Octave, such as computing
the inverse of a matrix, need to be very fast because it happens so
frequently. But for code paths which are used infrequently, some slowness is
acceptable.
An example already in the Octave code base is our use of print_usage() when
input validation has failed. The function goes and reads the m-file as text,
finds and extracts just the Texinfo, calls out to the shell to run makeinfo on
the Texinfo source, and then presents it to the screen. That is very slow
indeed, but it doesn't matter because it is only used when an error has
occurred which isn't frequent.
The same thing applies here. Latex plots aren't made all the time and if they
take a little longer it is acceptable.
Regarding discrepancies between screen and printout, how bad will it be if the
programmer uses one of the standalone formats such as "pdflatexstandalone"? I
would think the consistency would be very high in this case.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?59546>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/