Re: using previous =#+results= when =:eval never=

2021-07-04 Thread Berry, Charles
> On Jul 3, 2021, at 10:19 PM, Greg Minshall wrote: > > Chuck, > > thanks. (i'm not surprised at an e-lisp suggestion from you! :) > > i worry about accidental modification of the base case results during > the chaos of development. it occurs to me (reading through > (org-babel-ref-resolve

Re: using previous =#+results= when =:eval never=

2021-07-03 Thread Greg Minshall
Chuck, thanks. (i'm not surprised at an e-lisp suggestion from you! :) i worry about accidental modification of the base case results during the chaos of development. it occurs to me (reading through (org-babel-ref-resolve)) to keep my base case source blocks marked with [:results silent], whic

Re: using previous =#+results= when =:eval never=

2021-07-03 Thread Berry, Charles
> On Jul 3, 2021, at 9:35 AM, Greg Minshall wrote: > > hi. > > i am trying to simplify adding regression test cases to a program. > > to generate the base, "compared-to" results, i want to write some code > in a source block, then evaluate it, producing the "true" value. > > then, later dur

using previous =#+results= when =:eval never=

2021-07-03 Thread Greg Minshall
hi. i am trying to simplify adding regression test cases to a program. to generate the base, "compared-to" results, i want to write some code in a source block, then evaluate it, producing the "true" value. then, later during development, i want to check if the code that ran in that block gives