From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Gauland Subject: org-babel-sh and Microsoft Windows Date: Sun, 07 Feb 2010 08:10:58 +1300 (NZDT) Message-ID: <20100207.081058.49077221.mikelygee@no8wireless.co.nz> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ndq4W-000629-2o for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 14:12:00 -0500 Received: from [199.232.76.173] (port=58133 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ndq4V-00061z-Nt for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 14:11:59 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Ndq4U-0006dS-50 for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 14:11:59 -0500 Received: from jersey.rurallink.co.nz ([114.134.15.197]:44410 helo=smtp.rurallink.co.nz) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ndq4T-0006Xq-Kh for emacs-orgmode@gnu.org; Sat, 06 Feb 2010 14:11:57 -0500 Received: from 114-134-7-63.rurallink.co.nz ([114.134.7.63] helo=localhost) by smtp.rurallink.co.nz with esmtpsa (SSL3.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1Ndq41-0002Mi-Cq for emacs-orgmode@gnu.org; Sun, 07 Feb 2010 08:11:29 +1300 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I tried using org-babel-sh at work, where I run emacs under Microsoft Windows, but only received an oddly-formatted message about (quote sh) not being recognised as a command. After mucking around with org-babel-sh.el, I modified the call to shell-command-on-region, changing the hard-coded "sh" to (as I recall) "cmd /k"). This looks promising, but I wonder if there are any other changes I'll need to make. Also, would it be better to adapt org-babel-sh to handle Microsoft's "shell", or to implement a new org-babel "language"? Thanks for your advice, Mike