emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vladimir Nikishkin <lockywolf@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-scheme doesn't support :stdin?
Date: Tue, 21 Jan 2020 12:05:47 +0800	[thread overview]
Message-ID: <CA+A2iZbQB8pbBunmX5zu-kLMWOf0RXJPOw2XjwDFJ0ugnmYGDg@mail.gmail.com> (raw)
In-Reply-To: <87ftgdnypx.fsf@kyleam.com>

I just thought that practically speaking, I no interpreter should
really need stdin, right?
Since everything that is prepended with a shebang: #! interpreter
is at the same time a valid shell script, isn't it?

сб, 18 янв. 2020 г. в 13:02, Kyle Meyer <kyle@kyleam.com>:
>
> Vladimir Nikishkin <lockywolf@gmail.com> writes:
>
> > Is it true that ob-scheme doesn't support :stdin <blockname>?
> >
> > I just tried, and doesn't seem to work, although it works with ob-shell.
> >
> > (This is not a complaint, I just would like to confirm that I
> > understand things correctly.)
>
> Yes, that's true as far as I can tell:
>
>   $ git grep :stdin
>   lisp/ob-awk.el:;; - :stdin takes an Org data or code block reference, the value of
>   lisp/ob-awk.el:  (stdin (let ((stdin (cdr (assq :stdin params))))
>   lisp/ob-sed.el:  (stdin (let ((stdin (cdr (assq :stdin params))))
>   lisp/ob-shell.el:        (stdin (let ((stdin (cdr (assq :stdin params))))
>   testing/examples/ob-awk-test.org:#+begin_src awk  :stdin genseq :results silent
>   testing/examples/ob-sed-test.org:  #+BEGIN_SRC sed :stdin ex1
>
> So it seems support for :stdin is limited to awk, sed, and shell.



-- 
Yours sincerely, Vladimir Nikishkin

  reply	other threads:[~2020-01-21  4:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18  3:45 ob-scheme doesn't support :stdin? Vladimir Nikishkin
2020-01-18  5:02 ` Kyle Meyer
2020-01-21  4:05   ` Vladimir Nikishkin [this message]
2020-01-21 14:39     ` Neil Jerram

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=CA+A2iZbQB8pbBunmX5zu-kLMWOf0RXJPOw2XjwDFJ0ugnmYGDg@mail.gmail.com \
    --to=lockywolf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.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).