[FR] Adding explicitly negative :results Type option

[FR] Adding explicitly negative :results Type option

[Weaver Marquez]

There is behavior that only happens if `:results' Type is not set at all.
I'd like to request a new Type option that would easily negate a
default arg without having to clear the default header args variable.

By Type, I mean these:
<https://orgmode.org/manual/Results-of-Evaluation.html#Type-1>

Case 1: With no default header args
  ,---- elisp
  | (concat "My String")

  ,---- result
  | My String

Case 2: With default `:results scalar'

  ,---- elisp
  | (concat "My String")

  ,---- result
  | "My String"


Being new to Library of Babel, my default header args are
`:results value vector replace'. However, I had trouble with this
code block from `elot' used to add a SETUPFILE on HTML export:

`foo.org'
,----
| #+call: theme-readtheorg()
`----

`theme-readtheorg()'
,----
| (concat "#+SETUPFILE: " (file-name-directory (locate-library
"elot")) "theme-readtheorg.setup")
`----

Which won't work if the /Type/ value is set by default.

I think this would be useful even if the better solution is getting used
to setting buffer/header local variables. It could also help library authors
ensure that a certain code block like above will work as intended.

Re: [FR] Adding explicitly negative :results Type option

[Ihor Radchenko]

Weaver Marquez <weavermarquez0@gmail.com> writes:

> There is behavior that only happens if `:results' Type is not set at all.
> I'd like to request a new Type option that would easily negate a
> default arg without having to clear the default header args variable.
>
> By Type, I mean these:
> <https://orgmode.org/manual/Results-of-Evaluation.html#Type-1>
>
> Case 1: With no default header args
>   ,---- elisp
>   | (concat "My String")
>
>   ,---- result
>   | My String
>
> Case 2: With default `:results scalar'
>
>   ,---- elisp
>   | (concat "My String")
>
>   ,---- result
>   | "My String"
> ...
> I think this would be useful even if the better solution is getting used
> to setting buffer/header local variables. It could also help library authors
> ensure that a certain code block like above will work as intended.

What about introducing an additional :results Type option - :results
auto? We will also make it the default.

Then, you can use :results auto to override whatever result type is
inferred from parent heading/global option/variable.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>