[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [BUG] ob-shell: internal representation of cmdline arguments the sam
From: |
Ihor Radchenko |
Subject: |
Re: [BUG] ob-shell: internal representation of cmdline arguments the same |
Date: |
Mon, 29 Apr 2024 12:22:09 +0000 |
Matt <matt@excalamus.com> writes:
> #+begin_src bash :cmdline 1 2 3
> ...
> #+begin_src bash :cmdline "1 2 3"
> ...
> It was stated that,
>
> #+begin_quote
> AFAICT, it's due to how headers are parsed by
> 'org-babel-parse-header-arguments' using 'org-babel-read'. The cell "\"1 2
> 3\"" (corresponding to :cmdline "1 2 3") is reduced through 'string-match' to
> "1 2 3". The cell "1 2 3" (corresponding to :cmdline 1 2 3), on the other
> hand, passes through. The result is that :cmdline "1 2 3" and :cmdline 1 2 3
> become indistinguishable.
> #+end_quote
Yes, "1 2 3" and 1 2 3 are the same from the perspective of header arg
parser - on purpose.
The idea is to allow passing arbitrary Elisp objects are values
:header-argument #("fancy" 0 1 (invisible t))
:cmdline "string object"
:foo '(a b c)
To force quotes in the :cmdline one can do
#+begin_src bash :cmdline "\"1 2 3\""
echo "$1"
#+end_src
#+RESULTS:
: 1 2 3
Not a bug.
Canceled.
--
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>