Linux Command Line Client : GET leaves "<feff>&qu

James Jeffers · Post by **James Jeffers** » Tue Sep 13, 2005 10:03 am

I'm noticing that a GET leaves

<feff>

as the first characters in files.

Any ideas as to why this is?

bfinney · Post by **bfinney** » Tue Sep 13, 2005 10:46 am

Yeah, we noticed this recently as well, while looking at the issue reported here: http://support.sourcegear.com/viewtopic.php?t=4632.

The stream header is being written into the file on disk, which formerly didn't happen. We're guessing that something may have changed in mono, but don't know for sure yet.

It is logged against the next release (3.1.3), so it should be addressed soon.

James Jeffers · Post by **James Jeffers** » Tue Sep 13, 2005 10:54 am

Just as a side note, I am hoping that somehow these mono issues are perculating to the top of the PITA list.

I've said it before, and while I'm not trying to be mean about it the support folks, this needs to be said. Please, please, please move away from mono. Provide a real, honest-to-goodness binary client for Linux and Solaris.

Wrap it up in a pretty package, like an rpm or Solaris package, that can be added, upgraded, or removed with a single command.

The reliance on a third-party implementation for the core functionality of your client is painful.

James Jeffers · Post by **James Jeffers** » Tue Oct 04, 2005 6:29 am

Any updates as to the availability of 3.13?

dan · Post by **dan** » Tue Oct 04, 2005 7:20 am

It will probably be sometime this month...

James Jeffers · Post by **James Jeffers** » Fri Oct 07, 2005 8:30 am

I noticed a very old forum thread on using Mono and the command line client. I added LC_CTYPE=POSIX to the environmet, and the "feff" characters did not appear on a GET.

I'll keep working with the client, and if this seems to be resolved, I'll post another reply later on.

Post by **jclausius** » Tue Nov 29, 2005 9:53 am

James:

A quick update - Based on this thread, we spotted an issue where .Net on Mono was putting Byte Order Marks in text files.

This will be fixed in the soon to be released Vault 3.1.6.