emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] ob-shell-test, test-ob-shell and introduction


From: Max Nikulin
Subject: Re: [PATCH] ob-shell-test, test-ob-shell and introduction
Date: Thu, 6 Jan 2022 00:12:28 +0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0

On 01/01/2022 02:18, Matt wrote:

  > Wow.  Nice work!

Thanks. I pushed things to Worg, if you haven't seen already
(https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html).
If you read it and find anything missing or unclear, please let me
know.

Thank you, I was not aware of ":cmdline" argument and of ":shebang" as a means to avoid stray prompts (I have seen mentions of similar problem for other languages in this list).

I have noticed some glitches.

- https://www.mirbsd.org/pics/logo-grey.png works only with http: protocol for me. - I am unsure concerning example after "…or as a standlone script.", maybe it should be wrapped into #+begin_example. - In some cases "sh" is used despite bashisms in the code like "declare" or "echo -ne". Actually "printf" may be more convenient instead of "echo -n" - "export" in session example is unnecessary. It is matter of taste though. Bash and dash is not the case, but some shells require that assignment and export should be separate commands. - In your examples variable values are simple. Often it is safer to add double quotes around variable or command expansion. I would consider adding quotes just to encourage people to do the same by default with hope that less scripts will give strange results in response to a file name containing a space. Actually my first impression was that backslashes before quotes in some cases were added by mistake. Another unescaped pair of quotes may make your intention more clear. However it is related to code style where everybody has opinion, so I do not insist.






reply via email to

[Prev in Thread] Current Thread [Next in Thread]