Removed the quasi-useless gtk2rc file and the documentation that went with it. Now CoqIDE is not anymore totally irrespectful of the local configuration of themes, in particular w.r.t. to menu fonts.

git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/coq/trunk@15251 85f007b7-540e-0410-9357-904b9bb8a0f7

2 files changed, 10 insertions, 46 deletions

diff --git a/doc/faq/FAQ.tex b/doc/faq/FAQ.tex
index 0bd84992bd..b5a4c160da 100644
--- a/doc/faq/FAQ.tex
+++ b/doc/faq/FAQ.tex
@@ -2342,20 +2342,13 @@ rendering tool provided by the server (see
 
 \Question{How to enable Emacs keybindings?}
 
-Depending on your configuration, use either one of these two methods
-
-\begin{itemize}
-
-\item Insert \texttt{gtk-key-theme-name = "Emacs"}
-    in your \texttt{coqide-gtk2rc} file. It should be in
-    \verb#$XDG_CONFIG_DIRS/coq# dir. This is done by default.
-
-\item If in Gnome, run the gnome configuration editor (\texttt{gconf-editor})
+If in Gnome, run the gnome configuration editor (\texttt{gconf-editor})
 and set key \texttt{gtk-key-theme} to \texttt{Emacs} in the category
 \texttt{desktop/gnome/interface}.
 
-\end{itemize}
-
+Otherwise, you need to find where the \verb#gtk-key-theme-name# option is located in
+your configuration, and set it to \texttt{Emacs}. Usually, it is in the
+\verb#$(HOME)/.gtkrc-2.0# file.
 
 
 %$ juste pour que la coloration emacs marche
@@ -2406,33 +2399,14 @@ keycode  26 = e E e E U2203 NoSymbol U2203 NoSymbol
 \end{verbatim}
 and then run xmodmap ~/.xmodmaprc.
 
-	Alternatively, if your version of \verb=xmodmap= does not support unicode, you need to use something like
-\begin{verbatim}
-xmodmap -e "keycode  24 = a A F13 F13"
-xmodmap -e "keycode  26 = e E F14 F14"
-\end{verbatim}
-	and then to add
-
-\verb=bind "F13" {"insert-at-cursor" ("=$\forall$\verb=")}=\\
-\verb=bind "F14" {"insert-at-cursor" ("=$\exists$\verb=")}=
-
-	to your "binding "text"" section in \verb#coqiderc-gtk2rc#.
-	The last arguments to {\tt bind} between "" are
-        the UTF-8 encodings for 0x2200 and 0x2203.
-	You can compute these encodings using the lablgtk2 toplevel with
-\begin{verbatim}		
-Glib.Utf8.from_unichar 0x2200;;
-\end{verbatim}
-	Further symbols can be bound on higher Fxx keys or on even on other keys you
-	do not need .
-\end{itemize}
+	Alternatively, you may use an input method editor such as SCIM or iBus.
+The latter offers a \LaTeX-like input method.
 
 \Question{How to customize the shortcuts for menus?}
  Two solutions are offered:
 \begin{itemize}
 \item Edit \verb+$XDG_CONFIG_HOME/coq/coqide.keys+ (which is usually \verb+$HOME/.config/coq/coqide.keys+) by hand or
-\item Add "gtk-can-change-accels = 1" in your coqide-gtk2rc file. Then
-    from \CoqIde, you may select a menu entry and press the desired 
+\item If your system supports it, from \CoqIde, you may select a menu entry and press the desired 
     shortcut. 
 \end{itemize}
 
diff --git a/doc/refman/RefMan-ide.tex b/doc/refman/RefMan-ide.tex
index f061ef18d4..e0c6c868f7 100644
--- a/doc/refman/RefMan-ide.tex
+++ b/doc/refman/RefMan-ide.tex
@@ -209,21 +209,11 @@ Notice that these settings are saved in the file \verb|.coqiderc| of
 your home directory. 
 
 A gtk2 accelerator keymap is saved under the name \verb|.coqide.keys|.
-This file should not be edited manually: to modify a given menu
+It is not recommanded to edit this file manually: to modify a given menu
 shortcut, go to the corresponding menu item without releasing the
 mouse button, press the key you want for the new shortcut, and release
-the mouse button afterwards.
-
-For experts: it is also possible to set up a specific gtk resource
-file, under the name \verb|.coqide-gtk2rc|, following the gtk2
-resources syntax
-\url{http://developer.gnome.org/doc/API/2.0/gtk/gtk-Resource-Files.html}.
-Such a default resource file can be found in the subdirectory
-\verb=lib/coq/ide= of the root installation directory of \Coq{}
-(alternatively, it can be found in the subdirectory \verb=ide= of the
-source archive of \Coq{}). You may
-copy this file into your home directory, and edit it using any text
-editor, \CoqIDE{} itself for example.
+the mouse button afterwards. If your system does not allow it, you may still 
+edit this configuration file by hand, but this is more involved.
 
 \section{Using unicode symbols}