doc: Remove references to GTK.

We don't support it.

Author: sethjackson

runtime/doc/change.txt

@@ -832,13 +832,13 @@ This replaces each 'E' character with a euro sign.  Read more in |<Char->|.
 :promptf[ind] [string]
 			Put up a Search dialog.  When [string] is given, it is
 			used as the initial search string.
-			{only for Win32 and GTK GUI}
+			{only for Win32 GUI}
 
 						*:promptr* *:promptrepl*
 :promptr[epl] [string]
 			Put up a Search/Replace dialog.  When [string] is
 			given, it is used as the initial search string.
-			{only for Win32 and GTK GUI}
+			{only for Win32 GUI}
 
 
 4.4 Changing tabs					*change-tabs*
@@ -1171,18 +1171,6 @@ See |quotestar| and |quoteplus|.  When the clipboard is not available or not
 working, the unnamed register is used instead.  For Unix systems and Mac OS X,
 see |nvim-clipboard|.
 
-						*quote_~* *quote~* *<Drop>*
-The read-only "~ register stores the dropped text from the last drag'n'drop
-operation.  When something has been dropped onto Vim, the "~ register is
-filled in and the <Drop> pseudo key is sent for notification.  You can remap
-this key if you want; the default action (for all modes) is to insert the
-contents of the "~ register at the cursor position.
-{only available when compiled with the |+dnd| feature, currently only with the
-GTK GUI}
-
-Note: The "~ register is only used when dropping plain text onto Vim.
-Drag'n'drop of URI lists is handled internally.
-
 9. Black hole register "_				*quote_*
 When writing to this register, nothing happens.  This can be used to delete
 text without affecting the normal registers.  When reading from this register,

runtime/doc/cmdline.txt

@@ -492,7 +492,6 @@ followed by another Vim command:
     :function
     :global
     :help
-    :helpfind
     :lcscope
     :ldo
     :lfdo

runtime/doc/editing.txt

@@ -1145,7 +1145,7 @@ If you want to always use ":confirm", set the 'confirm' option.
 			|:diffsplit|, |:diffpatch|, |:pedit|, |:redir|,
 			|:source|, |:update|, |:visual|, |:vsplit|,
 			and |:qall| if 'confirm' is set.
-			{only in Win32, GTK and Mac GUI}
+			{only in Win32 and Mac GUI}
 			When ":browse" is not possible you get an error
 			message.  If the |+browse| feature is missing or the
 			{command} doesn't support browsing, the {command} is
@@ -1173,16 +1173,13 @@ For versions of Vim where browsing is not supported, the command is executed
 unmodified.
 
 							*browsefilter*
-For MS Windows and GTK, you can modify the filters that are used in the browse
-dialog.  By setting the g:browsefilter or b:browsefilter variables, you can
-change the filters globally or locally to the buffer.  The variable is set to
-a string in the format "{filter label}\t{pattern};{pattern}\n" where {filter
-label} is the text that appears in the "Files of Type" comboBox, and {pattern}
-is the pattern which filters the filenames.  Several patterns can be given,
-separated by ';'.
-
-For Motif the same format is used, but only the very first pattern is actually
-used (Motif only offers one pattern, but you can edit it).
+For Windows you can modify the filters that are used in the browse dialog.  By
+setting the g:browsefilter or b:browsefilter variables, you can change the
+filters globally or locally to the buffer.  The variable is set to a string in
+the format "{filter label}\t{pattern};{pattern}\n" where {filter label} is the
+text that appears in the "Files of Type" comboBox, and {pattern} is the
+pattern which filters the filenames.  Several patterns can be given, separated
+by ';'.
 
 For example, to have only Vim files in the dialog, you could use the following
 command: >

runtime/doc/eval.txt

@@ -2563,7 +2563,7 @@ confirm({msg} [, {choices} [, {default} [, {type}]]])
 		{default} is omitted, 1 is used.
 
 		The optional {type} argument gives the type of dialog.  This
-		is only used for the icon of the GTK, Mac, and Win32 GUI.  It
+		is only used for the icon of the Mac and Win32 GUI.  It
 		can be one of these values: "Error", "Question", "Info",
 		"Warning" or "Generic".  Only the first character is relevant.
 		When {type} is omitted, "Generic" is used.
@@ -3279,8 +3279,7 @@ foreground()	Move the Vim window to the foreground.	Useful when sent from
 		On Win32 systems this might not work, the OS does not always
 		allow a window to bring itself to the foreground.  Use
 		|remote_foreground()| instead.
-		{only in the Win32 and GTK GUI versions and the
-		Win32 console version}
+		{only in the Win32 GUI and console version}
 
 
 function({name})					*function()* *E700*
@@ -3528,8 +3527,6 @@ getfontname([{name}])					*getfontname()*
 		Only works when the GUI is running, thus not in your vimrc or
 		gvimrc file.  Use the |GUIEnter| autocommand to use this
 		function just after the GUI has started.
-		Note that the GTK 2 GUI accepts any font name, thus checking
-		for a valid name does not work.
 
 getfperm({fname})					*getfperm()*
 		The result is a String, which is the read, write, and execute
@@ -5213,8 +5210,7 @@ remote_foreground({server})				*remote_foreground()*
 		Note: This does not restore the window if it was minimized,
 		like foreground() does.
 		This function is not available in the |sandbox|.
-		{only in the Win32 and GTK GUI versions and the
-		Win32 console version}
+		{only in the Win32 GUI and the Win32 console version}
 
 
 remote_peek({serverid} [, {retvar}])		*remote_peek()*
@@ -6980,7 +6976,6 @@ debug			Compiled with "DEBUG" defined.
 dialog_con		Compiled with console dialog support.
 dialog_gui		Compiled with GUI dialog support.
 digraphs		Compiled with support for digraphs.
-dnd			Compiled with support for the "~ register |quote_~|.
 eval			Compiled with expression evaluation support.  Always
 			true, of course!
 ex_extra		Compiled with extra Ex commands |+ex_extra|.
@@ -6998,9 +6993,6 @@ fname_case		Case in file names matters (for Windows this is not
 folding			Compiled with |folding| support.
 gettext			Compiled with message translation |multi-lang|
 gui			Compiled with GUI enabled.
-gui_gnome		Compiled with Gnome support (gui_gtk is also defined).
-gui_gtk			Compiled with GTK+ GUI (any version).
-gui_gtk2		Compiled with GTK+ 2 GUI (gui_gtk is also defined).
 gui_mac			Compiled with Macintosh GUI.
 gui_running		Vim is running in the GUI, or it will start soon.
 gui_win32		Compiled with MS Windows Win32 GUI.

runtime/doc/gui.txt

@@ -593,10 +593,6 @@ The default menus have these priorities:
 When no or zero priority is given, 500 is used.
 The priority for the PopUp menu is not used.
 
-The Help menu will be placed on the far right side of the menu bar on systems
-which support this (GTK+).  For GTK+ 2, this is not done anymore
-because right-aligning the Help menu is now discouraged UI design.
-
 You can use a priority higher than 9999, to make it go after the Help menu,
 but that is non-standard and is discouraged.  The highest possible priority is
 about 32000.  The lowest is 1.
@@ -665,10 +661,8 @@ level.  Vim interprets the items in this menu as follows:
     toolbar button image.  Note that the exact filename is OS-specific: For
     example, under Win32 the command >
 	:amenu ToolBar.Hello :echo "hello"<CR>
-<   would find the file 'hello.bmp'.  Under GTK+/X11 it is 'Hello.xpm'.  With
-    GTK+ 2 the files 'Hello.png', 'Hello.xpm' and 'Hello.bmp' are checked for
-    existence, and the first one found would be used.
-    For MS-Windows and GTK+ 2 the bitmap is scaled to fit the button.  For
+<   would find the file 'hello.bmp'.  Under X11 it is 'Hello.xpm'.
+    For MS-Windows and the bitmap is scaled to fit the button.  For
     MS-Windows a size of 18 by 18 pixels works best.
     For MS-Windows the bitmap should have 16 colors with the standard palette.
     The light grey pixels will be changed to the Window frame color and the
@@ -717,8 +711,8 @@ nr  Name		Normal action  ~
 30  WinMinWidth		make current window use few columns
 
 					*hidden-menus* *win32-hidden-menus*
-In the Win32 and GTK+ GUI, starting a menu name with ']' excludes that menu
-from the main menu bar.  You must then use the |:popup| command to display it.
+In the Win32 GUI, starting a menu name with ']' excludes that menu from the
+main menu bar.  You must then use the |:popup| command to display it.
 
 							*popup-menu*
 You can define the special menu "PopUp".  This is the menu that is displayed
@@ -871,9 +865,8 @@ a menu item - you don't need to do a :tunmenu as well.
 
 5.9 Popup Menus
 
-In the Win32 and GTK+ GUI, you can cause a menu to popup at the cursor.
-This behaves similarly to the PopUp menus except that any menu tree can
-be popped up.
+In the Win32 GUI, you can cause a menu to popup at the cursor.  This behaves
+similarly to the PopUp menus except that any menu tree can be popped up.
 
 This command is for backwards compatibility, using it is discouraged, because
 it behaves in a strange way.
@@ -882,7 +875,7 @@ it behaves in a strange way.
 :popu[p] {name}			Popup the menu {name}.  The menu named must
 				have at least one subentry, but need not
 				appear on the menu-bar (see |hidden-menus|).
-				{only available for Win32 and GTK GUI}
+				{only available for Win32 GUI}
 
 :popu[p]! {name}		Like above, but use the position of the mouse
 				pointer instead of the cursor.

runtime/doc/helphelp.txt

@@ -184,12 +184,6 @@ command: >
 	:!xterm -e vim +help &
 <
 
-			*:helpfind* *:helpf*
-:helpf[ind]		Like |:help|, but use a dialog to enter the argument.
-			Only for backwards compatibility.  It now executes the
-			ToolBar.FindHelp menu entry instead of using a builtin
-			dialog.  {only when compiled with |+GUI_GTK|}
-
 					*:helpt* *:helptags*
 				*E154* *E150* *E151* *E152* *E153* *E670*
 :helpt[ags] [++t] {dir}

runtime/doc/index.txt

@@ -1241,7 +1241,6 @@ tag	      command	      action ~
 |:hardcopy|	:ha[rdcopy]	send text to the printer
 |:help|		:h[elp]		open a help window
 |:helpclose|	:helpc[lose]	close one help window
-|:helpfind|	:helpf[ind]	dialog to open a help window
 |:helpgrep|	:helpg[rep]	like ":grep" but searches help files
 |:helptags|	:helpt[ags]	generate help tags for a directory
 |:highlight|	:hi[ghlight]	specify highlighting methods

runtime/doc/mbyte.txt

@@ -97,14 +97,6 @@ is the difficult part.  It depends on the system you are using, the locale and
 a few other things.  See the chapters on fonts: |mbyte-fonts-X11| for
 X-Windows and |mbyte-fonts-MSwin| for MS-Windows.
 
-For GTK+ 2, you can skip most of this section.  The option 'guifontset' does
-no longer exist.  You only need to set 'guifont' and everything should "just
-work".  If your system comes with Xft2 and fontconfig and the current font
-does not contain a certain glyph, a different font will be used automatically
-if available.  The 'guifontwide' option is still supported but usually you do
-not need to set it.  It is only necessary if the automatic font selection does
-not suit your needs.
-
 For X11 you can set the 'guifontset' option to a list of fonts that together
 cover the characters that are used.  Example for Korean: >
 
@@ -484,11 +476,6 @@ For Vim you may need to set 'encoding' to "utf-8".
 Unfortunately, using fonts in X11 is complicated.  The name of a single-byte
 font is a long string.  For multi-byte fonts we need several of these...
 
-Note: Most of this is no longer relevant for GTK+ 2.  Selecting a font via
-its XLFD is not supported; see 'guifont' for an example of how to
-set the font.  Do yourself a favor and ignore the |XLFD| and |xfontset|
-sections below.
-
 First of all, Vim only accepts fixed-width fonts for displaying text.  You
 cannot use proportionally spaced fonts.  This excludes many of the available
 (and nicer looking) fonts.  However, for menus and tooltips any font can be
@@ -791,20 +778,6 @@ For example, when you are using kinput2 as |IM-server| and sh, >
 	export XMODIFIERS="@im=kinput2"
 <
 
-FULLY CONTROLLED XIM
-
-You can fully control XIM, like with IME of MS-Windows (see |multibyte-ime|).
-This is currently only available for the GTK GUI.
-
-Before using fully controlled XIM, one setting is required.  Set the
-'imactivatekey' option to the key that is used for the activation of the input
-method.  For example, when you are using kinput2 + canna as IM Server, the
-activation key is probably Shift+Space: >
-
-	:set imactivatekey=S-space
-
-See 'imactivatekey' for the format.
-
 ==============================================================================
 8.  Input on MS-Windows					*mbyte-IME*
 
@@ -1142,14 +1115,12 @@ internally.
 
 Vim has comprehensive UTF-8 support.  It works well in:
 - xterm with utf-8 support enabled
-- Motif and GTK GUI
 - MS-Windows GUI
 - several other platforms
 
 Double-width characters are supported.  This works best with 'guifontwide' or
 'guifontset'.  When using only 'guifont' the wide characters are drawn in the
-normal width and a space to fill the gap.  Note that the 'guifontset' option
-is no longer relevant in the GTK+ 2 GUI.
+normal width and a space to fill the gap.
 
 							*bom-bytes*
 When reading a file a BOM (Byte Order Mark) can be used to recognize the
@@ -1219,8 +1190,6 @@ doesn't always work.  See the system specific remarks below, and 'langmenu'.
 
 USING UTF-8 IN X-Windows				*utf-8-in-xwindows*
 
-Note: This section does not apply to the GTK+ 2 GUI.
-
 You need to specify a font to be used.  For double-wide characters another
 font is required, which is exactly twice as wide.  There are three ways to do
 this:

runtime/doc/message.txt

@@ -401,12 +401,6 @@ You have used an ":unabbreviate" command with an argument which is not an
 existing abbreviation.  All variations of this command give the same message:
 ":cunabbrev", ":iunabbrev", etc.  Check for trailing white space.
 
->
-  /dev/dsp: No such file or directory
-
-Only given for GTK GUI with Gnome support.  Gnome tries to use the audio
-device and it isn't present.  You can ignore this error.
-
 							*E31*  >
   No such mapping