From: Andy Parkins <andyparkins@gmail•com>
To: git@vger•kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx•de>,
Johannes Sixt <johannes.sixt@telecom•at>
Subject: Re: MinGW port - initial work uploaded
Date: Tue, 23 Jan 2007 13:22:31 +0000 [thread overview]
Message-ID: <200701231322.32987.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701231227200.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Tuesday 2007 January 23 11:32, Johannes Schindelin wrote:
> Maybe we have to go the other way round, just as POSIX git does: instead
> of spawning the pager, we should _beginthread() the actual work, and
> execl() the pager.
What about just forgetting paged output under Windows? It's been a while, but
the only decent one that I ever found was LIST.COM, and that's probably
vanished now.
I haven't used Windows in a while, are pipes still as awful as they were?
That is to say they cheated and redirected output to a temporary file then
redirected that file to the input of the second process. The upshot of which
was you had to have the whole pipe complete before you could view the first
page of output.
I can well imagine that in Windows I would find the paged output more painful
than useful.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail•com
next prev parent reply other threads:[~2007-01-23 13:22 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 20:48 MinGW port - initial work uploaded Johannes Sixt
2007-01-19 22:47 ` Christian MICHON
[not found] ` <20070119234816.235726@dial-up-mi-89.lombardiacom.it>
2007-01-19 23:53 ` Michael
2007-01-20 3:31 ` Shawn O. Pearce
2007-01-20 9:24 ` Johannes Schindelin
2007-01-20 20:05 ` Johannes Sixt
2007-01-20 20:21 ` Christian MICHON
2007-01-22 13:06 ` Christian MICHON
2007-01-22 16:39 ` Linus Torvalds
2007-01-22 22:25 ` Christian MICHON
2007-02-08 8:17 ` H. Peter Anvin
2007-02-08 14:06 ` Christian MICHON
2007-02-08 17:22 ` H. Peter Anvin
2007-01-23 11:25 ` Johannes Schindelin
2007-01-23 13:08 ` Christian MICHON
2007-01-23 14:17 ` Johannes Schindelin
2007-01-23 15:37 ` Linus Torvalds
2007-01-23 15:45 ` Alex Riesen
2007-01-23 15:52 ` Johannes Schindelin
2007-01-23 15:56 ` Alex Riesen
2007-01-23 16:00 ` Johannes Schindelin
2007-01-23 15:53 ` Shawn O. Pearce
2007-01-23 15:49 ` Johannes Schindelin
2007-01-24 7:12 ` Nguyen Thai Ngoc Duy
2007-01-24 10:17 ` Johannes Schindelin
2007-01-24 16:42 ` Linus Torvalds
2007-01-24 21:08 ` Christian MICHON
2007-02-08 17:18 ` H. Peter Anvin
2007-01-22 20:27 ` Johannes Sixt
2007-01-22 22:20 ` Christian MICHON
2007-01-23 8:31 ` Christian MICHON
2007-01-23 11:32 ` Johannes Schindelin
2007-01-23 12:06 ` Jakub Narebski
2007-01-23 15:29 ` Shawn O. Pearce
2007-01-23 13:12 ` Christian MICHON
2007-01-23 14:18 ` Johannes Schindelin
2007-01-23 18:55 ` Christian MICHON
2007-01-23 19:18 ` Johannes Schindelin
2007-01-23 19:28 ` Johannes Schindelin
2007-01-23 13:22 ` Andy Parkins [this message]
2007-01-23 14:21 ` Johannes Schindelin
2007-01-23 15:06 ` Andy Parkins
2007-01-23 15:20 ` Johannes Schindelin
2007-01-23 16:24 ` Andy Parkins
2007-01-23 16:37 ` Johannes Schindelin
2007-01-23 17:02 ` Linus Torvalds
2007-01-23 17:07 ` Johannes Schindelin
2007-01-24 1:44 ` Junio C Hamano
2007-01-24 1:57 ` Johannes Schindelin
2007-01-24 5:05 ` Junio C Hamano
2007-01-24 10:24 ` Johannes Schindelin
2007-01-23 13:36 ` Nguyen Thai Ngoc Duy
2007-01-23 14:15 ` Johannes Schindelin
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=200701231322.32987.andyparkins@gmail.com \
--to=andyparkins@gmail$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=johannes.sixt@telecom$(echo .)at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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