From: Matt <matt@excalamus.com>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: "Max Nikulin" <manikulin@gmail.com>,
"emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: Re: [DISCUSSION] The meaning of :cmdline header argument across babel backends
Date: Wed, 01 May 2024 19:48:21 +0200 [thread overview]
Message-ID: <18f35458dc1.12b1098e95744256.2240855810530845420@excalamus.com> (raw)
In-Reply-To: <874jbkcmyg.fsf@localhost>
---- On Sat, 27 Apr 2024 12:53:25 +0200 Max Nikulin wrote ---
> On 26/04/2024 20:09, Ihor Radchenko wrote:
> > Max Nikulin writes:
> >
> >> However looking wider, I do not like that :cmdline for ob-shell has
> >> different meaning than for other languages, see e.g. ob-sql. Only for
> >> shell this parameter is treated as arguments of a *script*. In other
> >> cases :cmdline is used to specify arguments of *interpreter* and I think
> >> ob-shell should follow this convention.
> >
> > Alas, we already have the current state of affairs documented in
> > https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-shell.html#orge70bc7b
> >
> > So, no breaking changes.
Both points are valid.
I disagree with one aspect: we shouldn't use Worg as a source of truth. The argument holds based on historical behavior of :cmdline. AFAIU, Worg is a wiki which is open, more or less, to anyone. Worg contents, AFAIU, have not always undergone review. The manual should be the final authority. Fortunately, there's nothing in the manual about :cmdline.
---- On Mon, 29 Apr 2024 15:33:38 +0200 Ihor Radchenko wrote ---
> I like :script-args.
+ 1
> The counterpart should then be :interpreter-args?
Are we thinking of implementing these for other languages, beyond ob-shell? If not, I believe we should consider it. That may be a path to resolve the issues of consistency and backwards compatibility.
If we're looking at these as general headers, then I don't think "arg" is the correct term here since a switch may not take a value. For example, the "-r" option for Bash (IIUC).
Quick name ideas that aren't good yet may inspire better ones by inspiring disgust--:switches, :flags, :options, (using an "i" prefix for "interpreter") :iswitches, :iflags, :ioptions
--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode
next prev parent reply other threads:[~2024-05-01 17:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 15:54 [BUG] ob-shell: :shebang changes interpretation of :cmdline Max Nikulin
2023-11-18 18:09 ` Matt
2023-12-04 13:58 ` Ihor Radchenko
2023-12-04 20:41 ` Matt
2023-11-18 18:20 ` [BUG] ob-shell: :cmdline fails with single argument (was Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline) Matt
2023-11-19 6:57 ` Max Nikulin
2023-11-19 7:57 ` Matt
2024-04-21 15:09 ` [PATCH] Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline Matt
2024-04-23 10:28 ` Ihor Radchenko
2024-04-24 10:33 ` Max Nikulin
2024-04-24 12:52 ` Ihor Radchenko
2024-04-25 10:06 ` Max Nikulin
2024-04-26 11:49 ` Ihor Radchenko
2024-04-27 10:31 ` Max Nikulin
2024-04-27 13:37 ` Max Nikulin
2024-04-28 12:34 ` Ihor Radchenko
2024-04-23 10:51 ` Max Nikulin
2024-04-23 17:08 ` Max Nikulin
2024-04-26 13:09 ` [DISCUSSION] The meaning of :cmdline header argument across babel backends (was: [PATCH] Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline) Ihor Radchenko
2024-04-27 10:53 ` [DISCUSSION] The meaning of :cmdline header argument across babel backends Max Nikulin
2024-04-29 13:33 ` Ihor Radchenko
2024-05-01 17:48 ` Matt [this message]
2024-05-01 18:01 ` Ihor Radchenko
2024-05-02 18:50 ` Matt
2024-05-03 12:12 ` Ihor Radchenko
2024-04-26 13:12 ` [PATCH] Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline Ihor Radchenko
2024-04-27 7:43 ` Matt
2024-04-27 7:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18f35458dc1.12b1098e95744256.2240855810530845420@excalamus.com \
--to=matt@excalamus.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=yantar92@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.