[Monotone-devel] wcswidth

2005-12-02 Thread Lapo Luchini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It seems that monotone's configure lacks a test for wcswidth: 0.24 compiles no more under FreeBSD 4.x, which doesn't supply it. I'll have some days away from home, I'll take a look at that (possibly writing a FreeBSD4-specific patch) next week.

Re: [Monotone-devel] wcswidth

2005-12-02 Thread Thomas Moschny
On Friday 02 December 2005 10:39, Lapo Luchini wrote: It seems that monotone's configure lacks a test for wcswidth: 0.24 compiles no more under FreeBSD 4.x, which doesn't supply it. I'll have some days away from home, I'll take a look at that (possibly writing a FreeBSD4-specific patch) next

[Monotone-devel] broken i18n : xgettext options

2005-12-02 Thread BenoƮt Dejean
Hi, i don't know if my system is broken, but xgettext no longer gets configured to scan for F()/FP(). LC_ALL=C intltool-update -x fr Working, please wait...Building monotone.pot... Running /usr/bin/xgettext --add-comments --directory=. --output=monotone.pot --files-from=./POTFILES.in.temp

[Monotone-devel] Re: Line endings produced by internal 3-way merge

2005-12-02 Thread graydon hoare
Joe Hull wrote: I believe I'm observing that when monotone successfully completes an internal three-way merge the resulting merged file always uses a LF as its line ending no matter what the line ending convention of the host system or the line endings of the three source files for the three-way

Re: [Monotone-devel] Re: Line endings produced by internal 3-way merge

2005-12-02 Thread Nathaniel Smith
On Fri, Dec 02, 2005 at 02:49:30PM -0800, graydon hoare wrote: Joe Hull wrote: I believe I'm observing that when monotone successfully completes an internal three-way merge the resulting merged file always uses a LF as its line ending no matter what the line ending convention of the host