unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: nalaginrut <nalaginrut@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: on the importance of names (was: proposal: enhance and rename guile-tools)
Date: Wed, 30 Mar 2011 21:15:22 +0800	[thread overview]
Message-ID: <1301490922.2690.6.camel@Renee-desktop> (raw)
In-Reply-To: <m38vvw50i6.fsf_-_@unquote.localdomain>

> Howdy,
> 
> On Mon 21 Mar 2011 00:16, ludo@gnu.org (Ludovic Courtès) writes:
> 
> > Andy Wingo <wingo@pobox.com> writes:
> >
> >> "Guido, compile my-file.scm."
> >
> > Is the pun[*] intended?  :-)
> 
> OK, point taken.  Too bad though!
> 
> I have another proposal, but first I want to elaborate on why I think
> guile-tools is a silly name.
> 
> First of all it's not a good noun.  I don't know how to capitalize it,
> for example.  Guile-Tools ?  Too camel-casey.  Guile-tools ?  It's long
> and slanted, like a boat launching ramp.  guile-tools ?  But then it
> doesn't look like the start of a sentence.
> 
> Also, how do you feel when you say "guile-tools compile foo.scm" ?  I
> kinda feel like a tool!  Its clunkiness makes me feel clunky.  Not good!
> 
> These difficulties have real repercussions.  A clunky name leads us to
> avoid mentioning the thing, which isn't good either for the tool itself
> or for peoples' awareness of the tool.
> 
> Names are important, is what I'm saying.
> 
> So!  My new proposal is "guild".
> 
>   guild update
>   guild compile foo.scm
>   guild install fmt
> 

My girl friend think "guile-tool" could be abbreviate to 
"guil+t"=guilt...just joking, I don't think that's a proper name...hope
not enraging somebody. :-)



-- 
GNU Powered it
GPL Protected it
GOD Blessed it

HFG - NalaGinrut

--hacker key--
v4sw7CUSMhw6ln6pr8OSFck4ma9u8MLSOFw3WDXGm7g/l8Li6e7t4TNGSb8AGORTDLMen6g6RASZOGCHPa28s1MIr4p-x hackerkey.com
---end key---




  parent reply	other threads:[~2011-03-30 13:15 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
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 [this message]
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=1301490922.2690.6.camel@Renee-desktop \
    --to=nalaginrut@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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).