From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Problem with #+BEGIN_SRC shell, and export Date: Tue, 10 Dec 2013 11:53:30 -0700 Message-ID: <8738m0r0yq.fsf@gmail.com> References: <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]:55545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqSSe-0005Bk-Nb for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 13:55:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VqSSa-0002G6-DW for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 13:55:12 -0500 Received: from mail-pb0-x22b.google.com ([2607:f8b0:400e:c01::22b]:65431) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VqSSa-0002Cy-76 for emacs-orgmode@gnu.org; Tue, 10 Dec 2013 13:55:08 -0500 Received: by mail-pb0-f43.google.com with SMTP id rq2so8252017pbb.30 for ; Tue, 10 Dec 2013 10:55:07 -0800 (PST) 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: =?utf-8?Q?Fran=C3=A7ois?= Pinard Cc: emacs-orgmode@gnu.org Fran=C3=A7ois Pinard writes: > 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 > Perhaps one could add '("shell" . 'sh) to org-src-lang-modes. That would protect against this particular error. Whatever solution is adopted should be easily discovered and sidestepped in case anyone actually did want to export code using shell-mode for highlighting. Best, --=20 Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D