diff --git a/Fltk/fieldWindow.cpp b/Fltk/fieldWindow.cpp
index 12500f1c78eec3b7e503cd6eea7b51194bf9da88..e00f8b766baa81e8a28c7dfd56fe0b8d4a76f171 100644
--- a/Fltk/fieldWindow.cpp
+++ b/Fltk/fieldWindow.cpp
@@ -250,7 +250,7 @@ void fieldWindow::saveFieldOptions()
           if(istream >> a){
             if(a != ',')
               Msg::Error("Unexpected character \'%c\' while parsing option "
-                         "'%s' of field \'%s\'", a, it->first.c_str(), f->id);
+                         "'%s' of field \'%d\'", a, it->first.c_str(), f->id);
             sstream << ", ";
           }
         }
diff --git a/doc/VERSIONS.txt b/doc/VERSIONS.txt
index 7c740b286bc807f6396c663ccb68960f9b05f0c0..73e61115e1b0bf76607bd2e5692b2703060093ea 100644
--- a/doc/VERSIONS.txt
+++ b/doc/VERSIONS.txt
@@ -1,4 +1,6 @@
-$Id: VERSIONS.txt,v 1.33 2009-01-23 07:56:41 geuzaine Exp $
+$Id: VERSIONS.txt,v 1.34 2009-01-26 12:31:51 geuzaine Exp $
+
+2.3.1 (?): new per-window visibility.
 
 2.3.0 (Jan 23, 2009): major graphics and GUI code refactoring; new
 full-quad/hexa subdivision algorithm (removed Mesh.RecombineAlgo);
diff --git a/doc/texinfo/gmsh.texi b/doc/texinfo/gmsh.texi
index f03453c09e50f7a13b9af58f2d0c0b3b7dc46a21..5acfdc6718f14b09fbcf40c7da6f00d6b6a500ac 100644
--- a/doc/texinfo/gmsh.texi
+++ b/doc/texinfo/gmsh.texi
@@ -2489,14 +2489,15 @@ zero (e.g., @code{Solver.ClientServer0 = 0}). This doesn't require any
 modification to be made to the solver.
 
 If you want the solver to interact with Gmsh (for error messages, option
-definitions, post-processing, etc.), you need to link your solver with the
-@file{GmshClient.c} file and add the appropriate function calls inside your
-program. You can then proceed as in the previous case, but this time you
-should set the client-server option to 1 (e.g., @code{Solver.ClientServer0 =
-1}), so that Gmsh and the solver can communicate through a Unix socket. See
-@ref{Solver example}, for an example of how to interface a C++
-solver. Bindings for solvers written in other languages (C, Perl and Python)
-are available in the source distribution.
+definitions, post-processing, etc.), you need to include
+@file{GmshSocket.h} in your code and add the appropriate function calls
+inside your program. You can then proceed as in the previous case, but
+this time you should set the client-server option to 1 (e.g.,
+@code{Solver.ClientServer0 = 1}), so that Gmsh and the solver can
+communicate through a Unix socket. See @ref{Solver example}, for an
+example of how to interface a C++ solver. Bindings for solvers written
+in other languages (C, Perl and Python) are available in the source
+distribution.
 
 @menu
 * Solver options::