From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Fran=C3=A7ois_Pinard?= Subject: Problem with #+BEGIN_SRC shell, and export Date: Thu, 05 Dec 2013 23:58:52 -0500 Message-ID: <87r49qpoc3.fsf@iro.umontreal.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58552) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqQoJ-0003gP-8d for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 12:09:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqQoD-0003nF-AW for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 12:09:27 -0500 Received: from 206-248-137-202.dsl.teksavvy.com ([206.248.137.202]:58827 helo=mercure.progiciels-bpi.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqQoD-0003n5-6Y for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 12:09:21 -0500 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi, Org people. Let me make this report from memory, now that I'm back home! :-) In an Org file, a coworker used "#+BEGIN_SRC shell" where he should have written "#+BEGIN_SRC sh". While this looks like a benign error to me, it broke my publishing script, and I did not figure at once what was happening. At export time, when Emacs is called in batch, the export procedure dies. Emacs says that some process disappeared, and I think I got that the batch Emacs tries to start "M-x shell" under the scene. Could the HTML exporter (or all of them) protect itself (themselves) better? Or else, maybe, if this is a reasonable to do, could Org tell us, somehow, whenever a source mode (like "shell", here) is "wrong"? Fran=C3=A7ois