"git tfs help <command>" fails when using MinTTY or other non-conhost console with cygwin about git-tfs

[spraints]

This also happens if you git tfs help pull | less in git bash. Very annoying. A fix is most welcome.

[JamesDunne]

Lol, love the subtle undertone of "please fix it for me". :)

As I mentioned it looks to be internal to CSharpOptParse. I did look into it a little bit but concluded that I'd have to hack that library to fix it. Did you know they use embedded XSLT templates as assembly resources in order to translate your UsageBuilder into text or HTML form? Shocking, and a little disgusting. If I find some time I'll look into it.

[spraints]

yeah, i was a little shocked and appalled at what i found in there when i went to figure out what was going on.

[jedidja]

Running a normal command prompt, I also get a similar error:

C:\git>git-tfs help fetch 
Usage: git-tfs fetch [options] [tfs-remote-id]...
Function 'ext:FormatText()' has failed.
Attempt by method 'System.Xml.Xsl.XsltOld.XsltCompileContext+FuncExtension.Invoke(System.Xml.Xsl.XsltContext, System.Object[], System.Xml.XPath.XPathNavigator)'
to access method 'CommandLine.OptParse.UsageBuilder+TextTransformHelper.FormatText(System.String, Int32, Int32)' failed.

[rbanks54]

@jedidja change the "git-tfs" in your command to "git tfs", i.e. without the dash, and try again. git-tfs is a git plugin, not a command of it's own.

[jedidja]

Oh -- oops :) I kept wondering why all the examples had 'git tfs' instead of 'git-tfs'. That still throws the same error though

Jedidja@SKYFIRE-PC /c/git
$ git tfs help fetch
Usage: git-tfs fetch [options] [tfs-remote-id]...
Function 'ext:FormatText()' has failed.
Attempt by method 'System.Xml.Xsl.XsltOld.XsltCompileContext+FuncExtension.Invoke(System.Xml.Xsl.XsltContext, System.Object[], System.Xml.XPath.XPathNavigator)'
 to access method 'CommandLine.OptParse.UsageBuilder+TextTransformHelper.FormatText(System.String, Int32, Int32)' failed.

[nylen]

I have had good luck with the NDesk options library - it's nice and simple:

http://www.ndesk.org/Options

[spraints]

Cool. That looks like a good replacement for the current option parser.

[nulltoken]

I have had good luck with the NDesk options library - it's nice and simple:

As stated by @migueldeicaza here, NDesk.Options is now distributed as part as Mono.

If the licencing is compatible, you may be willing to reuse the parser, which keeps on being maintained by the original author @jonpryor.

[nylen]

As far as I can tell, the licenses are compatible. The library is MIT-licensed, and from http://apache.org/legal/resolved.html#category-a:

Works under the following licenses may be included within Apache products:

• [...]
• MIT/X11
• [...]

@nulltoken, the file you linked to is all there is to the library anyway.

[nulltoken]

@nulltoken, the file you linked to is all there into the library anyway.

@nylen Yes, indeed. However, NDesk.Options hasn't been updated in two years and is considered as Unstable by its author. Mono version of the code is kept up to date. I've checked and Mono.Options library looks like to be MIT licenced as well.

You can find the whole project here.

[jonpryor]

I don't consider NDesk.Options as Unstable. I just lost access to ndesk.org and can't connect back with Alp Toker to update the ndesk.org version. :-(

The only difference between the two, literally, is a #define. If you look at Options.cs, the NDESK_OPTIONS #define check on line 148 allows you to change the namespace (https://github.com/mono/mono/blob/2602f1367e4d1d9ae2207ed13040e3594dc40121/mcs/class/Mono.Options/Mono.Options/Options.cs#L148). That's the only difference between Mono.Options and NDesk.Options.

[nulltoken]

I don't consider NDesk.Options as Unstable.

@jonpryor Sorry for the misunderstanding. I wasn't trying to put words in your mouth. I was only refering to different minor things.

• the web site stating The NDesk.Options.dll assembly is currently UNSTABLE..
• the release note for version 0.2.1 which was posted on Oct, 20th 2008.
• the latest commit at git.ndesk.org was somewhat old compared to the latest Mono version.

I just lost access to ndesk.org

Sorry to hear this. This explains that.

The only difference between the two, literally, is a #define.

Ok, but... the commit log in the Mono repository still show some activity since the latest published NDesk version. Or am I mistaken?

However thanks a lot for your amazing work with this lib!

[jonpryor]

There are different definitions of "stable." Above, I mean that it's "stable" as in "it has no known bugs, won't corrupt your app, and is usable."

Previously, I said that NDesk.Options/Mono.Options had an unstable API, meaning that I reserve (and still reserve) the right to make API incompatible changes if/when necessary.

I still want to consider the API to be unstable, though I don't intend on changing the API.

What does this mean, practically speaking? It means that you shouldn't strong-name Mono.Options.dll and install it into the GAC, and you should instead bundle either the source or the assembly with your app. That's all.

[nulltoken]

@jonpryor Thanks for this very clear explanation!

A very last point: Was I correct when I previously mentioned that the git.ndesk.org repository is no longer up-to-date and that when bundling the source, one should rather use the mono repository?

[jonpryor]

@nulltoken Yes, you're correct that the git.ndesk.org repository is no longer up to date. I'd update it if I could, but I've been unable to locate Alp so that I can update it...

[nulltoken]

@jonpryor Thanks for having taken the time to bare with me :) And for making the world a better place with your commitment to Mono.

[spraints]

I started swapping out option parsing over the weekend.

[spraints]

please re-open if this problem isn't resolved.

[sc68cal]

Looks good to me - awesome work @spraints