Re: [O] Problem with #+BEGIN_SRC shell, and export
On Fri, 03 Jan 2014 15:53:34 +0100
Bastien wrote:
> Hi,
>
> Eric Schulte 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
signature.asc
Description: PGP signature
Re: [O] Problem with #+BEGIN_SRC shell, and export
Hi,
Eric Schulte 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.
--
Bastien
Re: [O] Problem with #+BEGIN_SRC shell, and export
François 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çois
>
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,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
[O] Problem with #+BEGIN_SRC shell, and export
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çois
