Hi Eric, Eric Schulte wrote: >> Now, subquestion: let's suppose I first write this code block... >> >> #+begin_src sh :exports results >> echo "I want to see this in HTML/PDF, but not in Org" >> #+end_src >> >> #+results: >> | I want to see this in HTML/PDF | but not in Org | >> >> then I add the option "silent", and eval it: >> >> #+begin_src sh :results silent :exports results >> echo "I want to see this in HTML/PDF, but not in Org" >> #+end_src >> >> #+results: >> | I want to see this in HTML/PDF | but not in Org | >> >> The =results= line is not removed automatically. I have to delete it myself. >> >> Question: wouldn't it be better to check, when option is =silent=, that >> there is >> no =results= line, and remove it if there is one? >> > > I tried implementing this change (a simple one-line addition) but it > breaks some other pieces of code block evaluation (inline blocks) which > assume that ":results silent" will not affect the contents of the > buffer. > > For not at least I think it would be preferable to leave the meaning of > silent to be "do nothing to the buffer" rather than to remove any > possibly pre-existing results. Possibly at some point in the future > after I've fixed results removal for inline blocks we should revisit > this decision.
Fine with me. Thanks for trying! Best regards, Seb -- Sebastien Vauban
