emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Vladimir Nikishkin <lockywolf@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Shouldn't ob-shell's org-babel-expand-src-block prepend the :shebang value?
Date: Sat, 05 Sep 2020 07:00:31 +0200	[thread overview]
Message-ID: <87y2loakcw.fsf@gnu.org> (raw)
In-Reply-To: <CA+A2iZZ1vMmKiUf4Fem1AU7CA1m9GQap+BkvrOsz+0BxRt6rRA@mail.gmail.com> (Vladimir Nikishkin's message of "Fri, 13 Mar 2020 09:03:10 +0800")

Hi Vladimir,

Vladimir Nikishkin <lockywolf@gmail.com> writes:

> I use C-c C-v C-v quite often to check the final file produced.
> I use ob-shell with the :shebang of "#!/usr/bin/chibi-scheme", because
> my code is actually scheme-script, and I need to use :stdin, which
> isn't supported by ob-scheme and geiser. (And geiser also has some not
> inconveniences).
>
> However, when I expand the block, the shebang line is not added to the
> top. The top line could also be potentially used for file type
> detection, and what is also annoying, errors reported by the
> interpreter are off by 1 (due to the missing first line).

can you share your suggestion as a patch?  It will be easier to read
it and evaluate its relevance.  If you need directions on how to share
a patch, let us know.

Thanks!

-- 
 Bastien


  reply	other threads:[~2020-09-05  5:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  1:03 Shouldn't ob-shell's org-babel-expand-src-block prepend the :shebang value? Vladimir Nikishkin
2020-09-05  5:00 ` Bastien [this message]
     [not found]   ` <CA+A2iZbJrNC3Rx5oAvyamBM_BObP8bxyTiFKtzxDrJhqe1MKsQ@mail.gmail.com>
     [not found]     ` <87d030ae7g.fsf@bzg.fr>
2020-09-10  6:52       ` Vladimir Nikishkin
2020-09-10  7:10         ` Tom Gillespie
2020-09-10  7:29           ` Vladimir Nikishkin
2020-09-10  7:30         ` Tim Cross

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=87y2loakcw.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lockywolf@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).