@FaheemMitha there are answers on site doing things like column sums, or setting colours based on cell values just using tex, you don't really need lua, although it's easier if you start with a simpler markup like a csv table rather than tex markup (see eg datatool package) if doing it in lua you could parse the input source looking for & and split up the lines using Lua patterns, but harder to cope with any macros in the table cells then.
@FaheemMitha yes, but as David says, it depends on your table. If all your table lines looks clean 1&2&3\\ it is easy. But if you have \bfseries 1&\itshape 2&\multicolumn{1}{|c|}{\textcolor{red!50!blue}{3}}\\ then it could be a bit difficult.
@FaheemMitha Not sure what you mean by that. If you mean the standard error output (a.k.a. stderr in C and many other languages, file descriptor 2), I don't think (lua)tex uses it at all. But here is an experiment from an interactive luatex showing what happens:
*\directlua{error("foo")}
[\directlua]:1: foo
stack traceback:
[C]: in function 'error'
[\directlua]:1: in main chunk.
<*> \directlua{error("foo")}
?
@HaraldHanche-Olsen What I mean is that standard error (in Lua) should be passed on to TeX. In practical terms, this means that if there is an error in Lua, TeX will halt.
I think this must be the case, because TeX is already halting for me on Lua errors, though I'm not actually checked how it is set up.
@HaraldHanche-Olsen And yes, I guess that is compelling evidence.
Here we see Lua's awe-inspiringly detailed traceback. (Don't mean to be snippy, but sometimes it can get a little tiresome.)
Actually, in this case, it's relatively reasonable, since it's just throwing from the error function.
@FaheemMitha lua.org/pil/8.3.htmlBecause Lua is an extension language, frequently embedded in an application, it cannot simply crash or exit when an error happens. Instead, whenever an error occurs, Lua ends the current chunk and returns to the application. If you want to catch errors look at the pcall function.
@FaheemMitha use xpcall to control how much of the stack trace is exposed on errors
@FaheemMitha look at the example at the end of latex.ltx that traps any errors from loading luaotfload if there are any it just sets the encoding back to OT1 but it could raise a tex error message or do anything else
@FaheemMitha Yes, it's wrapped up in an xpcall and there is an if statement checking the return value of that call. The else branch is executed if the call failed.
@FaheemMitha No, a reporter reporting on the case of the pair of Canadian murder suspects being chased across the country for the past week or so. (They've now been found dead.)
@tjt263 you haven't said what you want the over-wide table to be centred on, centred on the text block encroaching on both margins by the same amount? or (a bit harder as you have to account for the page parity) centred on the page even if the text block is not centred. I'm sure there are multiple answers on site for both.
@yo' Yes, that's true. The U (which on a map is really lying on its side) connects some mainly Hispanic neighbourhoods in Chicago. theconversation.com/…