emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: processing a literal example line by line in a shell source block?
Date: Fri, 4 Nov 2022 10:15:25 +0700	[thread overview]
Message-ID: <tk204d$75q$1@ciao.gmane.io> (raw)
In-Reply-To: <122789.1667413045@archlinux>

On 03/11/2022 01:17, Greg Minshall wrote:
> hi.  i have a text in a named #+begin_example ... #+end_example block.
> i would like to process this text line by line in a shell (bash, say)
> code block.  but, it appears that the individual lines are not
> separated, but passed as one long string to the source block.  (example
> below.)
> 
> #+name: lbl
> #+begin_example
> line 1
> line 2
> #+end_example

You may use :stdin instead of :var, see 
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html

#+begin_src bash :stdin lbl
   while read -r -a arr ; do
       printf 'value\t%s\n' "${arr[1]}"
   done
#+end_src

#+RESULTS:
| value | 1 |
| value | 2 |

> #+begin_src bash :var input=lbl :var in2='("first" "second")
>    echo ${#input[@]}
>    echo ${#in2[@]}
>    echo ${input}
> #+end_src

There is a nice tool: shellcheck. It should not be difficult to define a 
function that feeds current source block to it. The only point is to 
specify shell type since shebang is missed. In some cases even bash -n 
before running a script may save some time during debugging.





      parent reply	other threads:[~2022-11-04  3:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 18:17 processing a literal example line by line in a shell source block? Greg Minshall
2022-11-03  7:41 ` Ihor Radchenko
2022-11-04  2:14   ` Greg Minshall
2022-11-07  1:38   ` Greg Minshall
2022-11-04  3:15 ` Max Nikulin [this message]

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='tk204d$75q$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).