unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Long command line arguments using SRFI 37
Date: Sat, 5 Jan 2019 14:22:53 +0100	[thread overview]
Message-ID: <CAJ98PDxi4pBpo5Uh22ejHUCX9FUeLOR4SFe4d28LfZzosOep0g@mail.gmail.com> (raw)
In-Reply-To: <b7051c6d-b00a-8edc-697a-909775816595@gmail.com>

Il giorno ven 4 gen 2019 alle ore 19:55 Zelphir Kaltstahl <
zelphirkaltstahl@gmail.com> ha scritto:

> 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"
>
> It is not really a big issue, but I think it would still be great to
> have a way of allowing the first style as well, as I just spend an hour
> or so trying to figure out what was wrong with my program, until I took
> a look at my example code (see link below) again and checked how it
> behaved with style 1 and noticed it has the same error.
>
> 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
>
> Maybe I am missing something or doing something wrong?
>
> Regards,
>
> Zelphir
>
>
Hi Zelphir,

I can't help you with the processing of arguments with Guile, as I don't
know the first thing about that

I want to thank you for collecting that set of examples and tutorials

I only skimmed through the macro section and it seems quite interesting

Examples are very important and the Guile documentation sorely misses some
examples

Also, I also had the experience to struggle and waste lots of time with
Guile for quite simple things, too

For example, it too me some years to learn the usage of readline for a
better REPL experience (this information is sinked deep in the manual)

It also too me a long time to get the gist of the "eval buffer" command in
Geiser

You might be interested in this talk
https://archive.fosdem.org/2017/schedule/event/legacy_docs/

There is another library of examples that Tantalum pointed me to, this one
https://github.com/sph-mn/sph-lib/tree/master/modules/sph/server

Together with yours, this material is becoming meaningful, if not
substantive

Maybe the Guile website could point to these collections, maybe they could
be merged into one library only, we'll see

For now I just wanted to acknowledge your effort

Thanks


  parent reply	other threads:[~2019-01-05 13:22 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
2019-01-05 13:22 ` Catonano [this message]
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=CAJ98PDxi4pBpo5Uh22ejHUCX9FUeLOR4SFe4d28LfZzosOep0g@mail.gmail.com \
    --to=catonano@gmail.com \
    --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).