Re: [gnu-prog-discuss] url's in --help output

2009-01-22 Thread Neil Jerram
2009/1/22 Simon Josefsson : > Here it is. The module name and source filenames are rather long, but I > couldn't think of anything better. Untested, beware! > +void > +emit_bug_reporting_address (void) > +{ > + /* TRANSLATORS: The placeholder indicates the bug-reporting address > + for this

Re: [gnu-prog-discuss] url's in --help output

2009-01-22 Thread Neil Jerram
2009/1/22 Simon Josefsson : > > I don't follow? The comment is aimed at translators, and translators > will add the 'Report translation bugs ...' line in the particular > gettext translation file. Thus, source code is not modified. Thanks, I understand now. I thought the instruction meant to ad

Error in make info

2009-06-06 Thread Neil Jerram
relevant.) Regards, Neil >From 8e8413b17216352a99f6c409b7de16f58b740ef6 Mon Sep 17 00:00:00 2001 From: Neil Jerram Date: Fri, 5 Jun 2009 23:42:52 +0100 Subject: [PATCH] Escape non-texinfo { and }s --- doc/ld-output-def.texi |6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/ld-output-def

read() and write() for MinGW

2010-03-28 Thread Neil Jerram
I'd like to contribute a gnulib module to handle the fact that, on MinGW, you have to use recv() to read data from a socket, instead of read(). Similarly, for writing, send() is needed instead of write(). Conceptually this is extremely simple, and I've found that gnulib already contains useful bi

Re: read() and write() for MinGW

2010-03-29 Thread Neil Jerram
Paolo Bonzini writes: >>> Conceptually this is extremely simple, and I've found that gnulib >>> already contains useful bits like SOCKET_TO_FD, FD_TO_SOCKET, and the >>> code for determining if an arbitrary fd is a socket - which is all >>> great. >> >> Yes, and the read() and write() functions d