unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: proposal: enhance and rename guile-tools
Date: Mon, 21 Mar 2011 21:50:52 +0000	[thread overview]
Message-ID: <87ipvcf8hv.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <m3ei60tgrb.fsf@unquote.localdomain> (Andy Wingo's message of "Mon, 21 Mar 2011 20:28:40 +0100")

Andy Wingo <wingo@pobox.com> writes:

> This is fun :)
>
> Here are a few threads the PLT folk had:
>
>    http://thread.gmane.org/gmane.lisp.scheme.plt.devel/2540
>    http://thread.gmane.org/gmane.lisp.scheme.plt.devel/2693/focus=2715
>    http://thread.gmane.org/gmane.lisp.scheme.plt.devel/2775

Well indeed, that pretty much covers the problem space, including my
thought above.

Some further Guile-specific thoughts, in no particular order.

- "gel" is short; and it's the name of Guile before it was Guile; and
  suggests sticking things together; and AFAIK isn't already being used
  for anything else; and has similar key positions as "gdo", so is
  equally easy to type.

- FWIW, the current differences between 'guile-tools THING . ARGS' and
  'guile -e "(@@ (scripts THING) main)" -- . ARGS" appear to be that

  1. the guile command eventually does (main (cons "guile" ARGS)),
  whereas guile-tools does (main . ARGS) (aka (apply main ARGS))

  2. the guile command runs the REPL afterwards.

- I think I might find guile-tools (as is) less bothering if its
  built-in commands (help, version and list) were rewritten as scripts
  themselves.  Then it would be clearer that the remaining code in
  guile-tools was just implementing the main-invocation convention for
  scripts/*.

(Incidentally I have a patch pending for scripts/README, to remove some
of the statements about that convention that are no longer true.)

On the overall point, of having a separate name instead of just "guile",
I think it just comes down to the observation that "because the `git'
experience seems definitive".  And I agree that it's hard to argue with
that.

Best wishes for reaching a decision on this!

      Neil



  reply	other threads:[~2011-03-21 21:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-19 11:36 proposal: enhance and rename guile-tools Andy Wingo
2011-03-20 23:16 ` Ludovic Courtès
2011-03-21  8:27   ` Andy Wingo
2011-03-21 11:51     ` nalaginrut
2011-03-21 11:58       ` nalaginrut
2011-03-21 12:16     ` Barry Fishman
2011-03-21 14:10       ` Neil Jerram
2011-03-21 19:28         ` Andy Wingo
2011-03-21 21:50           ` Neil Jerram [this message]
2011-03-30 10:51             ` Andy Wingo
2011-03-30 18:27               ` Neil Jerram
2011-03-21 16:32       ` dsmich
2011-03-21 15:12     ` David Pirotte
2011-03-21 15:00   ` Jose A. Ortega Ruiz
2011-03-30 11:08   ` on the importance of names (was: proposal: enhance and rename guile-tools) Andy Wingo
2011-03-30 13:11     ` Noah Lavine
2011-03-30 13:15     ` nalaginrut
2011-03-30 15:52     ` on the importance of names Ludovic Courtès
2011-03-30 16:25       ` Andy Wingo
2011-03-31  9:32         ` Ludovic Courtès
2011-05-31 20:38           ` Andy Wingo
2011-05-31 21:55             ` Ludovic Courtès
2011-03-30 18:11     ` Neil Jerram

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=87ipvcf8hv.fsf@ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).