[BUG] shell not working as sh?

[Daniele Pizzolli <dan@toel.it>]

Hello,

I remember that sh was renamed to shell some time ago.

But shell sometimes does not work, while sh does.

Is there a difference between the two (and when i should use one over
another?) or is it a bug?

The minimal example follows:

#+PROPERTY: header-args:shell  :dir /vagrant@127.0.0.1:/vagrant
#+PROPERTY: header-args:shell+ :exports both :results output verbatim replace

#+PROPERTY: header-args:sh  :dir /vagrant@127.0.0.1:/vagrant
#+PROPERTY: header-args:sh+ :exports both :results output verbatim replace

* setup

#+BEGIN_SRC sh
cat $HOME/.ssh/id_rsa.pub >> $HOME/.ssh/authorized_keys
# TODO accept the host key automatically or use StrictHostKeyChecking no
# not sure if tramp is smart enough to handle this by default
#+END_SRC

#+BEGIN_SRC emacs-lisp
(org-babel-do-load-languages
 'org-babel-load-languages
 '((emacs-lisp . t)
   (python . t)
   (shell . t)
   (sh . t)))
#+END_SRC

#+RESULTS:


#+RESULTS:

* sh works

#+BEGIN_SRC sh
ls | wc -l
#+END_SRC

#+RESULTS:
: 5


* shell does not work

#+BEGIN_SRC shell
ls | wc -l
#+END_SRC

Will show in *Messages*

org-babel-execute:shell: Wrong number of arguments: #[(session body &optional params stdin) [... binary code cut ...]

* org version

#+BEGIN_SRC emacs-lisp
(org-version nil t)
#+END_SRC

#+RESULTS:
: Org-mode version 8.3beta (release_8.3beta-860-ge4da74 @ /home/vagrant/.emacs.d/el-get/org-mode/lisp/)

Best,
Daniele