@JosephWright you converted an answer to a comment but isn't that the only answer (apart from close q as off topic or something?) tex.stackexchange.com/questions/186895/…
@egreg :) It occurred when I updated the bib file with a newer version and references a file in /tmp/ that isn't even present... the result looks OK, though
@egreg: You're always faster than me (tex.stackexchange.com/q/186910/5645). I let SE send me an email when a new symbol question is asked, and still there were 5 people faster closing the question than I was.
@egreg :-) I'm just wondering how you manage to be so active. I had to get up early today, because I'm currently in the US and my advisers (in Germany) want to talk with me. But no matter how early / late it is, you're always there (or David Carlisle). I think you (and David) have answered quite a lot of my questions, too.
@cgnieder I think the whole arguments part can be supressed. The whole idea is that a command is now a closure on itself, so you can write the logic inside. :)
Good evening, I have written the following (runable) arara-program, which creates a password-locked pdf with adjustable prohibited access rights.
!config
# GhostScript-ps2pdf password-security rule for arara
# version: 0.1b
# requires arara 3.0+
identifier: secure
name: Secure
command: <arara>...
@leonardocesar Eu acho que uma possibilidade para uso inline é definir a formatação na especificação de colunas ou utilizar hooks que definam a formatação de legendas; dessa forma, as informações não ficam dependentes de macros de layout. Outra possibilidade é a utilização de pacotes que manipulam dados externos, como datatool e pgfplotstable. Mas, no geral, o encargo de definir a interface entre os dados e a visualização deles é nossa. :)
@egreg a bit but it's only a rough estimate to allocate column widths it's not as if \let\[$ gives a fully acccurate measument of the size of a display math either.