From: Sharon Kimble <boudiccas@talktalk.net>
To: Bastien <bzg@gnu.org>
Cc: "François Pinard" <pinard@iro.umontreal.ca>,
emacs-orgmode@gnu.org, "Eric Schulte" <schulte.eric@gmail.com>
Subject: Re: Problem with #+BEGIN_SRC shell, and export
Date: Fri, 3 Jan 2014 15:10:10 +0000 [thread overview]
Message-ID: <20140103151010.5d8ab5b1@london> (raw)
In-Reply-To: <87mwjdce1d.fsf@bzg.ath.cx>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
On Fri, 03 Jan 2014 15:53:34 +0100
Bastien <bzg@gnu.org> wrote:
> Hi,
>
> Eric Schulte <schulte.eric@gmail.com> writes:
>
> > 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.
>
> In this particular case, I don't think adding
>
> '("shell" . 'sh)
>
> 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.
>
> As for making it easier to discover I don't know, the docstring
> seems complete enough to me.
>
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.
Sharon.
--
A taste of linux = http://www.sharons.org.uk
efever = http://www.efever.blogspot.com/
efever = http://sharon04.livejournal.com/
my git repo = https://bitbucket.org/boudiccas/dots
Debian testing, Fluxbox 1.3.5, LibreOffice 4.1.4.2
Registered Linux user 561944
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-01-03 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 4:58 Problem with #+BEGIN_SRC shell, and export François Pinard
2013-12-10 18:53 ` Eric Schulte
2014-01-03 14:53 ` Bastien
2014-01-03 15:10 ` Sharon Kimble [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140103151010.5d8ab5b1@london \
--to=boudiccas@talktalk.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=pinard@iro.umontreal.ca \
--cc=schulte.eric@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).