From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sharon Kimble Subject: Re: Problem with #+BEGIN_SRC shell, and export Date: Fri, 3 Jan 2014 15:10:10 +0000 Message-ID: <20140103151010.5d8ab5b1@london> References: <87r49qpoc3.fsf@iro.umontreal.ca> <8738m0r0yq.fsf@gmail.com> <87mwjdce1d.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/hJSNzEhGmM6uuq6kqRQ0ExI"; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vz6OP-00020D-WA for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 10:10:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vz6OL-0007o6-GI for emacs-orgmode@gnu.org; Fri, 03 Jan 2014 10:10:33 -0500 In-Reply-To: <87mwjdce1d.fsf@bzg.ath.cx> 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: Bastien Cc: =?UTF-8?B?RnJhbsOnb2lz?= Pinard , emacs-orgmode@gnu.org, Eric Schulte --Sig_/hJSNzEhGmM6uuq6kqRQ0ExI Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 03 Jan 2014 15:53:34 +0100 Bastien wrote: > Hi, >=20 > Eric Schulte writes: >=20 > > 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. >=20 > In this particular case, I don't think adding=20 >=20 > '("shell" . 'sh) >=20 > to `org-src-lang-modes' will help, as shell-mode is a mode for > shell interactions, not just shell editing. So the user probably > wanted sh-mode instead. >=20 > As for making it easier to discover I don't know, the docstring > seems complete enough to me. >=20 Also using 'foobar.sh' is deprecated in current-day bash scripting, it should just be 'foobar'. But one thing is always current, the shebang - #!/bin/bash. That, or whatever scripting language is being used bash/dash/zsh/whatever, it will always say '#!/bin/WHATEVER' applicable to its scripting language.=20 Sharon. --=20 =EF=BB=BFA taste of linux =3D http://www.sharons.org.uk efever =3D http://www.efever.blogspot.com/ efever =3D http://sharon04.livejournal.com/ my git repo =3D https://bitbucket.org/boudiccas/dots Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.4.2 Registered Linux user 561944 --Sig_/hJSNzEhGmM6uuq6kqRQ0ExI Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJSxtLaAAoJEDaBgBkK+INbkAoQAKl7xdzaXIXkpgVwdwnVVb8h 4VR2n+/pNWbohNAoXzAi+wpXKWxRltWV29dxY00jgd7QVd+itApaOmBGHt6YL17R qEzxL/qtTK75iyJiqRJU70mFto6EQIMgB6wtAi6QM7bViYSxuv4alYGL9AGsCDth EgdWLPzLtjW4qosi25P+LxftGkvSWSpaZmzxJ7ya5E4egJrN2OhtFQeB7UcUKCM3 KIZtXPBTrxpl/oa1dHsGbg/s3pMgd/xYa/TNwMrCizOA6CzSZo/OC5Q2nW5UFSaD E+92Klqeb7l3cBwPU46z0aPy7HmJ2fWB+H6nETqtGAdVlWkAuZ3cum7bQy7yYcLB ySOH71vMxs6rl6k6zK/iT8M8qoAVmf795FW5w+AoGpOyUVJm3c5NtrW622n/swAP dgjna/3VtXOuwzAZuTL6EA8UbBQzUuWlPMnz2CgccHggzHm/G2kRGF0AX0sbVbet e6fo0lAqwbpJL5yIqtNeJ5h24YdyFFRNtG1uSyK5ZY0s15saeScb3poVWXojeq+V 4cdMXBL8g50A6imrvWVSatuekHaYC7CtKX9IJphV0qwkUBUpE8MK5ssfvJMuxLaD q7nct0kvXAHFKHwqpeb/OF8q9J5kxUJIbV4/X607sO7RcAV7Nqb4wSKgzOquGaEu E8nLzsLBtcXqmBS8X0uz =Tl41 -----END PGP SIGNATURE----- --Sig_/hJSNzEhGmM6uuq6kqRQ0ExI--