Hi, On Mon, 28 Jan 2008, Shawn O. Pearce wrote:
> Johannes Schindelin <[EMAIL PROTECTED]> wrote: > > On Sun, 27 Jan 2008, Kirill wrote: > > > > > TODO Flesh out menu items provided to the user. > > > Personally, besides copy of Tortoise's items, relevant to Git, and few > > > push/pull/branch commands, I came up blank. So, what are directions? > > > > Another thing (and this concerns you, Shawn): there is this lovely > > program called git-gui, and it has most of what we will ever want to > > drive from git-cheetah. Is there any method to call git-gui such that > > it performs a certain command, or is there a chance to get such a > > method? > > Uhm, no, not in any current version of git-gui. It actually tries hard > to shutdown any communication ports so people cannot remotely send > random Tcl strings for the Tk engine to eval. :) ;-) I did not mean to remote control it, just to start it with a default action, such as "diff file <xyz> to HEAD", or "diff directory <xyz> to index". > In most cases GUI buttons are backed by a reasonably named Tcl proc, so > it shouldn't be too difficult to trigger certain common commands from > git-cheetah and have git-gui respond to them, e.g. "stage file" or > "push". > > I'm not a Windows hacker. Someone pull up the Tcl/Tk manuals and > see what we can use. There's some sort of COM integration thingy > I think, based on an ugly Windows command exchange protocol (dce?). > And there's always plain 'ole TCP/IP over the loopback interface. IMHO that would be too much. Just executing git-gui with a certain action should be enough. Ciao, Dscho
