From: Suhail Singh <suhailsingh247@gmail.com>
To: Matt <matt@excalamus.com>
Cc: "Suhail Singh" <suhailsingh247@gmail.com>,
"Org mailing list" <emacs-orgmode@gnu.org>
Subject: Re: ob-shell: async support in "shell" vs "bash"
Date: Sun, 16 Jun 2024 18:02:41 -0400 [thread overview]
Message-ID: <87frtczgu6.fsf@gmail.com> (raw)
In-Reply-To: <19022520f63.acdaef901507354.6362811776086159414@excalamus.com> (matt@excalamus.com's message of "Sun, 16 Jun 2024 20:32:01 +0200")
Matt <matt@excalamus.com> writes:
> :async should work for all shell types.
Thank you for confirming the expected behaviour.
> Are you finding that it's not?
No. However, on language-specific shell code blocks (e.g. "bash")
org-lint reports warnings.
> Regarding org-babel-header-args, "org-babel-header-args:shell" is
> explicitly set to '((async . ((yes no)))), it seems, to quiet the
> linter
Indeed, it does. For "shell" source blocks, but not for specific
language blocks such as "bash".
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=40d1352b
I believe there's a bug in that commit. Specifically, the commit
message states:
#+begin_quote
Propagate base `org-babel-header-args:shell'
to`org-babel-header-args:<shell-name>'.
#+end_quote
However, the code initializes org-babel-header-args:<shell-name> to nil,
instead.
> For other languages, such as "org-babel-header-args:bash", it's set to
> nil. AFAICT, what you see are simply the default values.
Indeed. It seems to me that the appropriate default for
org-babel-header-args:<shell-name> should be the same as that for
org-babel-header-args:shell , yet it's not.
> I'm curious, what caused you to notice this inconsistency?
Org-lint (in my specific case, I have it configured to run on save via
flycheck).
--
Suhail
next prev parent reply other threads:[~2024-06-16 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 2:33 ob-shell: async support in "shell" vs "bash" Suhail Singh
2024-06-16 18:32 ` Matt
2024-06-16 22:02 ` Suhail Singh [this message]
2024-06-17 15:36 ` Ihor Radchenko
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=87frtczgu6.fsf@gmail.com \
--to=suhailsingh247@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=matt@excalamus.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).