From: Carlo Strozzi <firstname.lastname@example.org> To: Paul Haahr <email@example.com> Cc: firstname.lastname@example.org Subject: Re: building rc on QNX4 Date: Mon, 8 May 2000 04:01:43 -0400 [thread overview] Message-ID: <20000508100143.A16243@tango.texne.com> (raw) In-Reply-To: <cV5qLT1N20@iadd.jivetech.com>; from email@example.com on Sun, May 07, 2000 at 01:46:31PM -0400 On Sun, May 07, 2000 at 01:46:31PM -0400, Paul Haahr wrote: >Carlo Strozzi wrote >> Even calling it by it's name, that is Rc, would be reasonable. The >> mixed-casing would make it unique enough. > >And is the absolute worst suggestion we've had so far. > >Some of us have happily used Byron's rc for nearly a decade (others have >used the Plan 9 version for even longer) and the name has worked well >for all that time. > >Please just forget about changing the name. If you want to use it with >another name, you know how to do it. But the name of the executbale is >rc, and changing that is not worth discussing. Apart from the fact that I didn't suggest to change its name, but just to add a symlink in the stock 'make install' stuff (9sh is the best one I've heard so far), it's interesting to see how that admittedly irrelevant topic spawned more replies than the other two in the same message, i.e. how about having a 'read' builtin and not exporting every sort of stuff to the environment by default. Even if I added such features myself -- I'm awful at C --, they would not be part of the standard distribution, that's why I'm asking for an opinion here. bye -carlo -- I can read MIME or uuencoded e-mail attachments in PDF, Postscript, HTML, RTF or text formats. Please do not send Word or Excel files.
next prev parent reply other threads:[~2000-05-08 9:03 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2000-05-04 8:45 Byron Rakitzis 2000-05-06 10:28 ` Carlo Strozzi 2000-05-07 17:46 ` Paul Haahr 2000-05-08 8:01 ` Carlo Strozzi [this message] 2000-05-06 16:35 ` Jeremy Fitzhardinge -- strict thread matches above, loose matches on Subject: below -- 2000-05-09 4:34 Smarasderagd 2000-05-11 12:26 ` Gert-Jan Vons 2000-05-08 15:23 Sam Roberts 2000-05-09 8:25 ` Carlo Strozzi 2000-05-08 15:15 Smarasderagd 2000-05-09 8:22 ` Carlo Strozzi 2000-05-08 10:19 Bengt Kleberg 2000-05-06 21:47 Byron Rakitzis 2000-05-04 13:46 Sam Roberts [not found] <firstname.lastname@example.org> 2000-04-26 15:02 ` Sam Roberts 2000-04-27 16:56 ` Scott Schwartz 2000-04-27 20:41 ` Sam Roberts 2000-04-27 17:39 ` Carlo Strozzi 2000-05-02 14:41 ` Tim Goodwin 2000-05-04 15:18 ` Carlo Strozzi 2000-05-08 8:29 ` Tim Goodwin 2000-05-08 8:58 ` Chris Siebenmann 2000-05-08 9:15 ` Tim Goodwin 2000-05-08 23:25 ` Stephen Tell 2000-05-08 11:50 ` David Luyer 2000-05-08 13:28 ` Carlo Strozzi
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20000508100143.A16243@tango.texne.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: building rc on QNX4' \ /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
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 NNTP newsgroup(s).