> Or do you mean to put it in the message text, and just label the
> buttons a/b/c
changed it like this
On 12/11/2012 08:30 AM, Denis Bitouzé wrote:
> Le lundi 10/12/12 à 23h42,
> Benito van der Zander<benito@...> a écrit :
>>> doesn't actually answer the question "Do you trust this
>> Well, you need to trust this document, to allow it to run a custom
>> command or to allow it to add a command to the allowed list for all
> But if the question is "Do you trust this document?", the answer should
> be "Yes", "No" or, at a pinch, "More or less" :) not "I want to run the
> command contained in one of magic comments of this document for either
> just this document or for all documents or for any document".
> In fact, I should say more: what we are asked is if we trust the
> command, not the document, hence:
>>> Finally, I suggest something like the following.
>>> 1. Warning and question:
>>> "The document %1 wants to override the command %2 with %3.
>>> What do you want to do (read carefully before choosing!)?"
>>> 2. Answers and warnings:
>>> (a) "Always run the overridden command on this document" (only
>>> if you trust this document!)
> if you trust this document! -> if you trust this command!
>>> (b) "Allow the overridden command to be used for all
>>> documents" (only if you trust all documents: should be avoided!)
> if you trust all documents -> if you actually want to run this command
> for all your documents (!)
>>> (c) "Don't use the command %3 and run the default one"
>> Isn't that way to long to fit on the buttons?
>> Or do you mean to put it in the message text, and just label the
>> buttons a/b/c
>>> (only if you trust all documents: should be avoided!)
>> It should not be always avoided.
>> It is not always shell-escape, it could be a harmless command (e.g.
>> run asymptote before compiling, use latex instead pdflatex, convert
>> eps to pdf...)
> Maybe harm options like shell-escape should be detected and treated in
> a special way with appropriate warnings. But anyway, it looks strange
> for me to decide at some point to run a given command for all (even
> future) documents: at least, there should be a simple way to revert the