From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: stardiviner <numbchild@gmail.com>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Org source block header argument :var does not support space separated string
Date: Sat, 20 Oct 2018 22:17:10 +0200 [thread overview]
Message-ID: <878t2sgypl.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87sh11htsy.fsf@gmail.com> (stardiviner's message of "Sat, 20 Oct 2018 17:05:33 +0800")
Hello,
stardiviner <numbchild@gmail.com> writes:
> Org source block header argument :var does not support quoted string with space separator like bellowing example:
>
> For example
>
> **** encrypt text -- ~<<< [TEXT]~
>
> #+NAME: base64 encrypt text
> #+begin_src sh
>
> base64 <<< "stardiviner <numbchild@gmail.com>" #+end_src
>
> #+RESULTS: base64 encrypt text
> : c3RhcmRpdmluZXIgPG51bWJjaGlsZEBnbWFpbC5jb20+Cg==
>
>
> **** decrypt text -- ~-d~
>
> #+begin_src sh :var encrypted="base64 encrypt text"
> # base64 -d <<< c3RhcmRpdmluZXIgPG51bWJjaGlsZEBnbWFpbC5jb20+Cg==
> base64 -d <<< $encrypted
> #+end_src
>
> If I use #+NAME: base64-encrypt-text and :var
> encrypted=base64-encrypt-text, then it works fine.
I cannot reproduce your issues, literally. It complains about
a redirection error or something.
Anyway, I tried the following block:
#+begin_src emacs-lisp :var encrypted="base64 encrypt text"
encrypted
#+end_src
and the output is
#+results:
: base64 encrypt text
which means there doesn't seem to be a problem with strings within
quotes.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-10-20 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 9:05 Org source block header argument :var does not support space separated string stardiviner
2018-10-20 20:17 ` Nicolas Goaziou [this message]
2018-10-22 0:48 ` stardiviner
2018-10-22 16:04 ` Berry, Charles
2018-10-23 11:39 ` stardiviner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t2sgypl.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).