From: "David A. Wheeler" <dwheeler@dwheeler.com>
To: git@vger.kernel.org
Subject: Removing command dispatcher (was Re: [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes)
Date: Thu, 21 Apr 2005 14:15:51 -0400 [thread overview]
Message-ID: <4267EDD7.1070103@dwheeler.com> (raw)
In-Reply-To: <pan.2005.04.21.02.48.19.802122@smurf.noris.de>
Matthias Urlichs wrote:
>Linus Torvalds wrote:
>
>
>
>>I realize that there is probably a law that there has to be a space, but I
>>actually personally use tab-completion all the time
>>
>>
It's very unusual, but I can't think of any crisis it causes.
One minor annoyance: Windows doesn't support #! magic headers,
and a very few-and-probably-ignorable old Unix systems don't either.
There, commands written in an interpreter like perl, python, or shell can't
be kicked off just by a #! reference at the top (standard Windows' shell is
incompatible anyway, so it's just as well in the case of shell).
I don't see this as a roadblock, though. On those systems, you could
create trivial stubs that just invoke the interpreter (e.g., perl) and the
real program. In the Windows case, you can use Windows' miserable
excuse for a command processor to do that very easily.
E.g., if "cg-update" is a Perl script, then you can create a file
"cg-update.bat":
perl \path\to\cg-update %*
(That requires Windows NT4 or better. MS-DOS didn't have %*, so you needed:
perl \path\to\cg-update %1 %2 %3 %4 %5 %6 %7 %8 %9
It's hard to imagine an MS-DOS git user though.)
--- David A. Wheeler
next prev parent reply other threads:[~2005-04-21 18:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 20:56 [ANNOUNCE] git-pasky-0.6.2 && heads-up on upcoming changes Petr Baudis
2005-04-20 21:03 ` Petr Baudis
2005-04-20 21:19 ` Greg KH
2005-04-20 21:51 ` Mike Taht
2005-04-20 21:58 ` Joshua T. Corbin
2005-04-20 21:51 ` Petr Baudis
2005-04-20 21:54 ` Randy.Dunlap
2005-04-20 22:07 ` Steven Cole
2005-04-20 22:09 ` Linus Torvalds
2005-04-20 22:28 ` Petr Baudis
2005-04-20 23:04 ` Greg KH
2005-04-21 0:14 ` Linus Torvalds
2005-04-21 1:12 ` Linus Torvalds
2005-04-21 3:35 ` Daniel Jacobowitz
2005-04-21 2:45 ` Sean
2005-04-21 4:00 ` Linus Torvalds
2005-04-21 4:22 ` Dave Jones
2005-04-21 5:08 ` Junio C Hamano
2005-04-21 4:28 ` Daniel Jacobowitz
2005-04-21 6:49 ` Petr Baudis
2005-04-21 14:21 ` Edgar Toernig
2005-04-21 16:42 ` Petr Baudis
2005-04-24 0:09 ` Paul Jackson
2005-04-21 5:14 ` Randy.Dunlap
2005-04-21 4:27 ` Sean
2005-04-21 5:29 ` Greg KH
2005-04-24 0:12 ` Paul Jackson
2005-04-21 2:48 ` Matthias Urlichs
2005-04-21 18:15 ` David A. Wheeler [this message]
2005-04-21 7:49 ` Ingo Molnar
2005-04-25 11:27 ` Andrew Morton
2005-04-21 2:53 ` Bryan Donlan
2005-04-21 7:36 ` Petr Baudis
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4267EDD7.1070103@dwheeler.com \
--to=dwheeler@dwheeler.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).