From: "Shawn O. Pearce" <spearce@spearce.org>
To: Mark Levedahl <mlevedahl@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>, git@vger.kernel.org
Subject: Re: [PATCH] gitk - restore operation of git-reset on Cygwin
Date: Fri, 23 May 2008 19:17:14 -0400 [thread overview]
Message-ID: <20080523231714.GY29038@spearce.org> (raw)
In-Reply-To: <48374F82.7050005@gmail.com>
Mark Levedahl <mlevedahl@gmail.com> wrote:
> >Paul Mackerras wrote:
> >>Are you using Tk 8.4 or 8.5? The man pages for 8.5 imply that the
> >>2>@1 form should work for all platforms, but maybe that wasn't true in
> >>8.4. If that's the case it's worth mentioning in the patch
> >>description.
>
> I just tried installation of ActiveState Tcl 8.4.16, put that on the
> Cygwin path, and gitk operates correctly without the patch. So, the
> issue seems to be entirely one of Cygwin's particular Tcl/Tk build,
> though whether that is due to the version or the odd attributes of its
> compilation I cannot say.
git-gui ran into this problem and uses the following procedure
anytime it wants both stdout and stderr:
proc _open_stdout_stderr {cmd} {
_trace_exec $cmd
if {[catch {
set fd [open [concat [list | ] $cmd] r]
} err]} {
if { [lindex $cmd end] eq {2>@1}
&& $err eq {can not find channel named "1"}
} {
# Older versions of Tcl 8.4 don't have this 2>@1 IO
# redirect operator. Fallback to |& cat for those.
# The command was not actually started, so its safe
# to try to start it a second time.
#
set fd [open [concat \
[list | ] \
[lrange $cmd 0 end-1] \
[list |& cat] \
] r]
} else {
error $err
}
}
fconfigure $fd -eofchar {}
return $fd
}
--
Shawn.
prev parent reply other threads:[~2008-05-23 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 3:00 [PATCH] gitk - restore operation of git-reset on Cygwin Mark Levedahl
2008-05-23 3:46 ` Paul Mackerras
2008-05-23 22:26 ` Mark Levedahl
2008-05-23 23:13 ` Mark Levedahl
2008-05-23 23:17 ` Shawn O. Pearce [this message]
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=20080523231714.GY29038@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mlevedahl@gmail.com \
--cc=paulus@samba.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.
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).