From: Greg Minshall <minshall@umich.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs script options
Date: Sat, 18 Nov 2023 11:36:52 -0800 [thread overview]
Message-ID: <7094.1700336212@archlinux> (raw)
In-Reply-To: <83cyw7m3rr.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> wrote:
> How would you pass these -F, -d, -V etc. options to Emacs, or use them
> in any other way in the script, whose contents is supposed to be an
> Emacs Lisp program? There's something I'm missing here. I asked my
> question because I thought you had a real-life example of a script you
> wanted to use, but in your response you don't show any such example.
> Can you show it?
in this case, the -F, -d, -V are aimed at the elisp code running in the
script, not for Emacs itself.
think of wanting to convert some random unix utility to run as an Emacs
script (rather than as a shell script, say), and trying to make the
command line options (and invocation) the same as the original shell
script. does that help clarify?
in my case, i have the beginnings of a shell script that is to set up
some state and then invoke Emacs to do some work (org mode stuff). its
projected getopt(1) strings look like
----
getopt -o "B:C:dhP:V" -l "base-dir:,config-file:,debug,help,publish-dir:,version"
----
presumably most of those options (especially the long ones) don't
conflict with any Emacs command line options. but, some might ("-d"
does, as it turns out).
i'd like the users (hah!) to be able to type
----
./random-script -d --base-dir ${PWD}/foo
----
rather than
----
./random-script -- -d --base-dir ${PWD}/foo
----
cheers, Greg
(truth in advertising: in addition to this *application*, i also -- for
this application, really -- wrote some emacs-getopt package that would
probably benefit from such a facility.)
next prev parent reply other threads:[~2023-11-18 19:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 3:13 (unknown) Greg Minshall
2023-11-18 7:05 ` (unknown) Jim Porter
2023-11-18 14:10 ` (unknown) -x behavior change Greg Minshall
2023-11-18 7:36 ` Emacs script options Eli Zaretskii
2023-11-18 14:38 ` Greg Minshall
2023-11-18 16:20 ` Eli Zaretskii
2023-11-18 19:36 ` Greg Minshall [this message]
2023-11-19 5:55 ` Eli Zaretskii
2023-11-27 3:29 ` Greg Minshall
2023-11-27 12:59 ` Eli Zaretskii
2023-11-27 19:32 ` Greg Minshall
2023-11-18 19:18 ` Sebastian Miele
2023-11-18 19:49 ` Greg Minshall
2023-11-19 21:39 ` Jens Schmidt
2023-11-19 21:47 ` Jens Schmidt
2023-11-20 1:19 ` Greg Minshall
2023-11-21 21:13 ` Jens Schmidt
2023-11-22 18:17 ` Sebastian Miele
2023-11-22 20:18 ` Jens Schmidt
2023-11-24 4:22 ` Greg Minshall
2023-11-26 18:07 ` Jens Schmidt
2023-11-20 6:10 ` Sebastian Miele
2023-11-20 20:10 ` Jens Schmidt
2023-11-21 8:51 ` Sebastian Miele
2023-11-19 5:04 ` Bob Rogers
2023-11-19 6:21 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7094.1700336212@archlinux \
--to=minshall@umich.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.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).