unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Amirouche Boubekki <amirouche@hypermove.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: guile-user@gnu.org,
	guile-user <guile-user-bounces+amirouche=hypermove.net@gnu.org>
Subject: Re: Long command line arguments using SRFI 37
Date: Fri, 04 Jan 2019 21:04:11 +0100	[thread overview]
Message-ID: <a7963ea3b5c89e10d4996c9e7d891bce@hypermove.net> (raw)
In-Reply-To: <b7051c6d-b00a-8edc-697a-909775816595@gmail.com>

Le 2019-01-04 19:55, Zelphir Kaltstahl a écrit :
> Hi Guile Users,
> 
> I have a question regarding the usage of SRFI 37. Is it possible to 
> have
> long arguments, which one can use as follows:
> 
> guile main.scm --argument value
> 
> This is what I am used to with other command line programs. It seems to
> me, when I use SRFI 37, I can only get it to allow the following style
> of command line arguments:
> 
> guile main.scm --argument=value
> guile main.scm --argument="some value"
> 

This is really not a big issue :)

> 
> I have the example code, where I am trying to use SRFI 37, on:
> 
> https://gitlab.com/zelphir-kaltstahl-projects/guile-scheme-tutorials-and-examples/blob/dev/command-line-arguments/using-srfi-37.scm
> 

Tx for sharing this piece of code I was wondering how to use srfi 37



  reply	other threads:[~2019-01-04 20:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 18:55 Long command line arguments using SRFI 37 Zelphir Kaltstahl
2019-01-04 20:04 ` Amirouche Boubekki [this message]
2019-01-05 13:22 ` Catonano
2019-01-07 14:08   ` Zelphir Kaltstahl
  -- strict thread matches above, loose matches on Subject: below --
2019-01-06 12:07 tantalum
2019-01-06 22:57 ` Zelphir Kaltstahl

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a7963ea3b5c89e10d4996c9e7d891bce@hypermove.net \
    --to=amirouche@hypermove.net \
    --cc=guile-user-bounces+amirouche=hypermove.net@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@gmail.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.
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).