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: Thu, 02 May 2024 20:50:28 +0200 [thread overview]
Message-ID: <18f3aa4c676.ae62768085345.7619655152678494644@excalamus.com> (raw)
In-Reply-To: <8734r1s96j.fsf@localhost>
---- On Wed, 01 May 2024 20:01:03 +0200 Ihor Radchenko wrote ---
> Matt matt@excalamus.com> writes:
>
> > 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.
>
> For babel backends specifically, WORG is _the_ documentation for the
> built-in backends. It is what we will eventually move to the official
> manual and it is what we point users to from the manual for now.
Okay, I didn't know we made an explicit reference.
> (2) nobody got around to actually move things to the manual.
I'd be happy to help with this. Discussion for another thread, though.
> > Are we thinking of implementing these for other languages, beyond
> > ob-shell?
>
> Yes. The title of this thread has "across babel backends" :)
:)
> > 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
>
> Emm... but "command line arguments". No?
I was thinking it'd be strange to have an "argument to an argument." However, the Bash man says things like "non-option arguments". It wasn't my intent to have an argument argument argument.
Since we're considering this for all babel backends, "interpreter-args" wouldn't describe gcc or other compilers. What about :command-args, :command-args, :cmd-args? "Command" is the only thing I can think of that describes all of the languages, other than maybe "binary" or "executable". Maybe we could simply use ":args"? Maybe ":meta-args" since gcc or bash is meta to the script/artifact?
--
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-02 18:51 UTC|newest]
Thread overview: 35+ 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-06-27 12:47 ` Ihor Radchenko
2024-06-27 13:00 ` [BUG] ob-shell may use /bin/sh instead of the specified shell when :cmdline is provided (was: [PATCH] Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline) Ihor Radchenko
2024-06-27 13:08 ` Ihor Radchenko
2024-04-23 10:51 ` [PATCH] Re: [BUG] ob-shell: :shebang changes interpretation of :cmdline 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
2024-05-01 18:01 ` Ihor Radchenko
2024-05-02 18:50 ` Matt [this message]
2024-05-03 12:12 ` Ihor Radchenko
2024-05-20 18:01 ` Matt
2024-05-21 10:28 ` Max Nikulin
2024-05-21 11:34 ` Ihor Radchenko
2024-06-27 14:57 ` 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
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=18f3aa4c676.ae62768085345.7619655152678494644@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 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).