+Note the capitalization of @code{Scrollbar} for the Athena widget.
+
+@node Q4.6.4, Q4.6.5, Q4.6.3, Display
+@unnumberedsubsec Q4.6.4: Moving the scrollbar can move the point; can I disable this?
+
+When I move the scrollbar in an XEmacs window, it moves the point as
+well, which should not be the default behavior. Is this a bug or a
+feature? Can I disable it?
+
+The current behavior is a feature, not a bug. Point remains at the same
+buffer position as long as that position does not scroll off the screen.
+In that event, point will end up in either the upper-left or lower-left
+hand corner.
+
+This cannot be changed.
+
+@node Q4.6.5, Q4.6.6, Q4.6.4, Display
+@unnumberedsubsec Q4.6.5: Scrolling one line at a time.
+
+Can the cursor keys scroll the screen a line at a time, rather than the
+default half page jump? I tend it to find it disorienting.
+
+Use the following:
+
+@lisp
+(setq scroll-step 1)
+@end lisp
+
+You can also change this with Customize. Select from the
+@code{Options} menu
+@code{Advanced (Customize)->Emacs->Environment->Windows->Scroll Step...}
+or type @kbd{M-x customize @key{RET} windows @key{RET}}.
+
+@node Q4.6.6, Q4.6.7, Q4.6.5, Display
+@unnumberedsubsec Q4.6.6: How can I turn off automatic horizontal scrolling in specific modes?
+
+Do @code{(setq truncate-lines t)} in the mode-hooks for any modes
+in which you want lines truncated.
+
+More precisely: If @code{truncate-lines} is nil, horizontal scrollbars
+will never appear. Otherwise, they will appear only if the value of
+@code{scrollbar-height} for that buffer/window/etc. is non-zero. If you
+do
+
+@lisp
+(set-specifier scrollbar-height 0)
+@end lisp
+
+then horizontal scrollbars will not appear in truncated buffers unless
+the package specifically asked for them.
+
+@node Q4.6.7, Q4.7.1, Q4.6.6, Display
+@unnumberedsubsec Q4.6.7: I find auto-show-mode disconcerting. How do I turn it off?
+
+@code{auto-show-mode} controls whether or not a horizontal scrollbar
+magically appears when a line is too long to be displayed. This is
+enabled by default. To turn it off, put the following in your
+@file{init.el}:
+
+@lisp
+(setq auto-show-mode nil)
+(setq-default auto-show-mode nil)
+@end lisp
+
+@unnumberedsec 4.7: The Gutter Tabs, The Progress Bar, Widgets
+
+@node Q4.7.1, Q4.7.2, Q4.6.7, Display
+@unnumberedsubsec Q4.7.1: How can I disable the gutter tabs?
+
+#### Write me.
+
+@node Q4.7.2, Q4.7.3, Q4.7.1, Display
+@unnumberedsubsec Q4.7.2: How can I disable the progress bar?
+
+#### Write me.
+
+@node Q4.7.3, Q4.7.4, Q4.7.2, Display
+@unnumberedsubsec Q4.7.3: There are bugs in the gutter or widgets.
+
+#### Write me.
+
+@node Q4.7.4, , Q4.7.3, Display
+@unnumberedsubsec Q4.7.4: How can I customize the gutter or gutter tabs?
+
+#### Write me.
+
+@node External Subsystems, Internet, Display, Top
+@unnumbered 5 Interfacing with the Operating System and External Devices
+
+This is part 5 of the XEmacs Frequently Asked Questions list. This
+section is devoted to the various ways that XEmacs interfaces with the
+operating system, with other processes and with external devices such
+as speakers and the printer.
+
+@menu
+5.0: X Window System and Resources
+* Q5.0.1:: Where is a list of X resources?
+* Q5.0.2:: How can I detect a color display?
+* Q5.0.3:: How can I get the icon to just say @samp{XEmacs}?
+* Q5.0.4:: How can I have the window title area display the full path?
+* Q5.0.5:: @samp{xemacs -name junk} doesn't work?
+* Q5.0.6:: @samp{-iconic} doesn't work.
+
+5.1: Microsoft Windows
+* Q5.1.1:: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
+* Q5.1.2:: How do I get Windows Explorer to associate a file type with XEmacs?
+
+5.2: Printing
+* Q5.2.1:: What do I need to change to make printing work?
+* Q5.2.2:: How can I print WYSIWYG a font-locked buffer?
+* Q5.2.3:: Getting @kbd{M-x lpr} to work with postscript printer.
+* Q5.2.4:: Can you print under MS Windows?
+
+5.3: Sound
+* Q5.3.1:: How do I turn off the sound?
+* Q5.3.2:: How do I get funky sounds instead of a boring beep?
+* Q5.3.3:: What are NAS and ESD (EsounD)?
+* Q5.3.4:: Sunsite sounds don't play.
+
+5.4: Running an Interior Shell, Invoking Subprocesses
+* Q5.4.1:: What is an interior shell?
+* Q5.4.2:: How do I start up a second shell buffer?
+* Q5.4.3:: Telnet from shell filters too much
+* Q5.4.4:: Strange things are happening in Shell Mode.
+* Q5.4.5:: XEmacs complains "No such file or directory, diff"
+* Q5.4.6:: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
+
+5.5: Multiple Device Support
+* Q5.5.1:: How do I open a frame on another screen of my multi-headed display?
+* Q5.5.2:: Can I really connect to a running XEmacs after calling up over a modem? How?
+* Q5.5.3:: How do I disable gnuserv from opening a new frame?
+* Q5.5.4:: How do I start gnuserv so that each subsequent XEmacs is a client?
+* Q5.5.5:: Is there a way to start a new XEmacs if there's no gnuserv running, and otherwise use gnuclient?
+@end menu
+
+@unnumberedsec 5.0: X Window System and Resources
+
+@node Q5.0.1, Q5.0.2, External Subsystems, External Subsystems
+@unnumberedsubsec Q5.0.1: Where is a list of X resources?
+
+Search through the @file{NEWS} file for @samp{X Resources}. A fairly
+comprehensive list is given after it.
+
+In addition, an @file{app-defaults} file @file{etc/Emacs.ad} is
+supplied, listing the defaults. The file @file{etc/sample.Xresources}
+gives a different set of defaults that you might consider for
+installation in your @file{~/.Xresources} file. It is nearly the same
+as @file{etc/Emacs.ad}, but a few entries are altered. Be careful about
+installing the contents of this file into your @file{.Xresources} (or
+legacy @file{.Xdefaults}) file if you use GNU Emacs under X11 as well.
+
+@node Q5.0.2, Q5.0.3, Q5.0.1, External Subsystems
+@unnumberedsubsec Q5.0.2: How can I detect a color display?
+
+You can test the return value of the function @code{(device-class)}, as
+in:
+
+@lisp
+(when (eq (device-class) 'color)
+ (set-face-foreground 'font-lock-comment-face "Grey")
+ (set-face-foreground 'font-lock-string-face "Red")
+ ....
+ )
+@end lisp
+
+@node Q5.0.3, Q5.0.4, Q5.0.2, External Subsystems
+@unnumberedsubsec Q5.0.3: How can I get the icon to just say @samp{XEmacs}?
+
+I'd like the icon to just say @samp{XEmacs}, and not include the name of
+the current file in it.
+
+Add the following line to your @file{init.el}:
+
+@lisp
+(setq frame-icon-title-format "XEmacs")
+@end lisp
+
+@node Q5.0.4, Q5.0.5, Q5.0.3, External Subsystems
+@unnumberedsubsec Q5.0.4: How can I have the window title area display the full path?
+
+I'd like to have the window title area display the full directory/name
+of the current buffer file and not just the name.
+
+Add the following line to your @file{init.el}:
+
+@lisp
+(setq frame-title-format "%S: %f")
+@end lisp
+
+A more sophisticated title might be:
+
+@lisp
+(setq frame-title-format
+ '("%S: " (buffer-file-name "%f"
+ (dired-directory dired-directory "%b"))))
+@end lisp
+
+That is, use the file name, or the dired-directory, or the buffer name.
+
+@node Q5.0.5, Q5.0.6, Q5.0.4, External Subsystems
+@unnumberedsubsec Q5.0.5: @samp{xemacs -name junk} doesn't work?
+
+When I run @samp{xterm -name junk}, I get an xterm whose class name
+according to xprop, is @samp{junk}. This is the way it's supposed to
+work, I think. When I run @samp{xemacs -name junk} the class name is
+not set to @samp{junk}. It's still @samp{emacs}. What does
+@samp{xemacs -name} really do? The reason I ask is that my window
+manager (fvwm) will make a window sticky and I use XEmacs to read my
+mail. I want that XEmacs window to be sticky, without having to use the
+window manager's function to set the window sticky. What gives?
+
+@samp{xemacs -name} sets the application name for the program (that is,
+the thing which normally comes from @samp{argv[0]}). Using @samp{-name}
+is the same as making a copy of the executable with that new name. The
+@code{WM_CLASS} property on each frame is set to the frame-name, and the
+application-class. So, if you did @samp{xemacs -name FOO} and then
+created a frame named @var{BAR}, you'd get an X window with WM_CLASS =
+@code{( "BAR", "Emacs")}. However, the resource hierarchy for this
+widget would be:
+
+@example
+Name: FOO .shell .container .BAR
+Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+@end example
+
+instead of the default
+
+@example
+Name: xemacs.shell .container .emacs
+Class: Emacs .TopLevelEmacsShell.EmacsManager.EmacsFrame
+@end example
+
+
+It is arguable that the first element of WM_CLASS should be set to the
+application-name instead of the frame-name, but I think that's less
+flexible, since it does not give you the ability to have multiple frames
+with different WM_CLASS properties. Another possibility would be for
+the default frame name to come from the application name instead of
+simply being @samp{emacs}. However, at this point, making that change
+would be troublesome: it would mean that many users would have to make
+yet another change to their resource files (since the default frame name
+would suddenly change from @samp{emacs} to @samp{xemacs}, or whatever
+the executable happened to be named), so we'd rather avoid it.
+
+To make a frame with a particular name use:
+
+@lisp
+(make-frame '((name . "the-name")))
+@end lisp
+
+@node Q5.0.6, Q5.1.1, Q5.0.5, External Subsystems
+@unnumberedsubsec Q5.0.6: @samp{-iconic} doesn't work.
+
+When I start up XEmacs using @samp{-iconic} it doesn't work right.
+Using @samp{-unmapped} on the command line, and setting the
+@code{initiallyUnmapped} X Resource don't seem to help much either...
+
+@email{ben@@xemacs.org, Ben Wing} writes:
+
+@quotation
+Ugh, this stuff is such an incredible mess that I've about given up
+getting it to work. The principal problem is numerous window-manager
+bugs...
+@end quotation
+
+@unnumberedsec 5.1: Microsoft Windows
+
+@node Q5.1.1, Q5.1.2, Q5.0.6, External Subsystems
+@unnumberedsubsec Q5.1.1: Does XEmacs rename all the @samp{win32-*} symbols to @samp{w32-*}?
+
+In his flavor of Emacs 20, Richard Stallman has renamed all the @samp{win32-*}
+symbols to @samp{w32-*}. Does XEmacs do the same?
+
+We consider such a move counter-productive, thus we do not use the
+@samp{w32} prefix. (His rather questionable justification was that he
+did not consider Windows to be a "winning" platform.) However, the name
+@samp{Win32} is not particularly descriptive outside the Windows world,
+and using just @samp{windows-} would be too generic. So we chose a
+compromise, the prefix @samp{mswindows-} for Windows-related variables
+and functions.
+
+Thus all the XEmacs variables and functions directly related to either
+the Windows GUI or OS are prefixed @samp{mswindows-} (except for a
+couple of debugging variables, prefixed @samp{debug-mswindows-}). From
+an architectural perspective, however, we believe that this is mostly a
+non-issue because there should be a very small number of
+window-systems-specific variables anyway. Whenever possible, we try to
+provide generic interfaces that apply to all window systems.
+
+@c not true:
+@c The user variables
+@c that share functionality with existing NT Emacs variables are be named
+@c with our convention, but we provide the GNU Emacs names as
+@c compatibility aliases.
+
+@node Q5.1.2, Q5.2.1, Q5.1.1, External Subsystems
+@unnumberedsubsec Q5.1.2: How do I get Windows Explorer to associate a file type with XEmacs?
+
+@unnumberedsubsubsec Associating a new file type with XEmacs.
+
+In Explorer select @samp{View->Options->File Types}, press @samp{[New
+Type...]} and fill in the dialog box, e.g.:
+
+@example
+ Description of type: Emacs Lisp source
+ Associated extension: el
+ Content Type (MIME): text/plain
+@end example
+
+then press @samp{[New...]} and fill in the @samp{Action} dialog box as
+follows:
+
+@example
+ Action:
+ Open
+
+ Application used to perform action:
+ D:\Full\path\for\xemacs.exe "%1"
+
+ [x] Use DDE
+
+ DDE Message:
+ open("%1")
+
+ Application:
+ <leave blank>
+
+ DDE Application Not Running:
+ <leave blank>
+
+ Topic:
+ <leave blank>
+@end example
+
+@unnumberedsubsubsec Associating an existing file type with XEmacs.
+
+In Explorer select @samp{View->Options->File Types}. Click on the file
+type in the list and press @samp{[Edit...]}. If the file type already
+has an @samp{Open} action, double click on it and fill in the
+@samp{Action} dialog box as described above; otherwise create a new
+action.
+
+If the file type has more than one action listed, you probably want to
+make the @samp{Open} action that you just edited the default by clicking on
+it and pressing @samp{Set Default}.
+
+Note for Windows 2000 users: Under Windows 2000, get to @samp{File Types}
+using @samp{Control Panel->Folder Options->File Types}.
+
+@unnumberedsec 5.2: Printing
+
+@node Q5.2.1, Q5.2.2, Q5.1.2, External Subsystems
+@unnumberedsubsec Q5.2.1: What do I need to change to make printing work?
+
+For regular printing there are two variables that can be customized.
+
+@table @code
+@item lpr-command
+This should be set to a command that takes standard input and sends
+it to a printer. Something like:
+
+@lisp
+(setq lpr-command "lp")
+@end lisp
+
+@item lpr-switches
+This should be set to a list that contains whatever the print command
+requires to do its job. Something like:
+
+@lisp
+(setq lpr-switches '("-depson"))
+@end lisp
+@end table
+
+For postscript printing there are three analogous variables to
+customize.
+
+@table @code
+@item ps-lpr-command
+This should be set to a command that takes postscript on standard input
+and directs it to a postscript printer.
+
+@item ps-lpr-switches
+This should be set to a list of switches required for
+@code{ps-lpr-command} to do its job.
+
+@item ps-print-color-p
+This boolean variable should be set @code{t} if printing will be done in
+color, otherwise it should be set to @code{nil}.
+@end table
+
+NOTE: It is an undocumented limitation in XEmacs that postscript
+printing (the @code{Pretty Print Buffer} menu item) @strong{requires} a
+window system environment. It cannot be used outside of X11.
+
+@node Q5.2.2, Q5.2.3, Q5.2.1, External Subsystems
+@unnumberedsubsec Q5.2.2: How can I print WYSIWYG a font-locked buffer?
+
+Font-lock looks nice. How can I print (WYSIWYG) the highlighted
+document?
+
+The package @code{ps-print}, which is now included with XEmacs, provides
+the ability to do this. The source code contains complete instructions
+on its use, in
+@file{$prefix/lib/xemacs/xemacs-packages/lisp/ps-print/ps-print.el},
+being the default location of an installed ps-print package.
+
+@node Q5.2.3, Q5.2.4, Q5.2.2, External Subsystems
+@unnumberedsubsec Q5.2.3: Getting @kbd{M-x lpr} to work with postscript printer.
+
+My printer is a Postscript printer and @code{lpr} only works for
+Postscript files, so how do I get @kbd{M-x lpr-region} and @kbd{M-x
+lpr-buffer} to work?
+
+Put something like this in your @file{init.el}:
+
+@lisp
+(setq lpr-command "a2ps")
+(setq lpr-switches '("-p" "-1"))
+@end lisp
+
+If you don't use a2ps to convert ASCII to postscript (why not, it's
+free?), replace with the command you do use. Note also that some
+versions of a2ps require a @samp{-Pprinter} to ensure spooling.
+
+@node Q5.2.4, Q5.3.1, Q5.2.3, External Subsystems
+@unnumberedsubsec Q5.2.4: Can you print under MS Windows?
+
+As of 21.4, printing works on Windows, using simply
+@samp{File->Print BUFFER...}, and can be configured with
+@samp{File->Page Setup...}.
+
+Prior to 21.4, there is no built-in support, but there are some clever
+hacks out there. If you know how, please let us know and we'll put it
+here.
+
+@unnumberedsec 5.3: Sound
+
+@node Q5.3.1, Q5.3.2, Q5.2.4, External Subsystems
+@unnumberedsubsec Q5.3.1: How do I turn off the sound?
+
+Add the following line to your @file{init.el}:
+
+@lisp
+(setq bell-volume 0)
+(setq sound-alist nil)
+@end lisp
+
+That will make your XEmacs totally silent---even the default ding sound
+(TTY beep on TTY-s) will be gone.
+
+You can also change these with Customize. Select from the
+@code{Options} menu @code{Advanced
+(Customize)->Emacs->Environment->Sound->Sound...} or type @kbd{M-x
+customize @key{RET} sound @key{RET}}.
+
+
+@node Q5.3.2, Q5.3.3, Q5.3.1, External Subsystems
+@unnumberedsubsec Q5.3.2: How do I get funky sounds instead of a boring beep?
+
+Make sure your XEmacs was compiled with sound support, and then put this
+in your @file{init.el}:
+
+@lisp
+(load-default-sounds)
+@end lisp
+
+@node Q5.3.3, Q5.3.4, Q5.3.2, External Subsystems
+@unnumberedsubsec Q5.3.3: What are NAS and ESD (EsounD)?
+
+@dfn{Network Audio System} (NAS) is a client-server sound library for X.
+
+@uref{http://radscan.com/nas.html}.
+
+To build XEmacs with it, use the @file{configure} flag
+@samp{--with-sound=nas} (@samp{--enable-sound=nas} in 21.5 or later).
+
+@dfn{Enlightened Sound Daemon} (ESD or EsounD) is yet another sound system.
+
+@uref{http://www.tux.org/~ricdude/EsounD.html}.
+
+To build XEmacs with it, use the @file{configure} flag
+@samp{--with-sound=esd} (@samp{--enable-sound=esd} in 21.5 or later).
+
+You can specify support for both with a flag like
+@samp{--with-sound=nas,esd} (@samp{--enable-sound=nas,esd} in 21.5 or
+later).
+
+@node Q5.3.4, Q5.4.1, Q5.3.3, External Subsystems
+@unnumberedsubsec Q5.3.4: Sunsite sounds don't play.
+
+I'm having some trouble with sounds I've downloaded from sunsite. They
+play when I run them through @code{showaudio} or cat them directly to
+@file{/dev/audio}, but XEmacs refuses to play them.
+
+@email{gutschk@@uni-muenster.de, Markus Gutschke} writes:
+
+@quotation
+[Many of] These files have an (erroneous) 24byte header that tells about
+the format that they have been recorded in. If you cat them to
+@file{/dev/audio}, the header will be ignored and the default behavior
+for /dev/audio will be used. This happens to be 8kHz uLaw. It is
+probably possible to fix the header by piping through @code{sox} and
+passing explicit parameters for specifying the sampling format; you then
+need to perform a 'null' conversion from SunAudio to SunAudio.
+@end quotation
+
+@unnumberedsec 5.4: Running an Interior Shell, Invoking Subprocesses
+
+@node Q5.4.1, Q5.4.2, Q5.3.4, External Subsystems
+@unnumberedsubsec Q5.4.1: What is an interior shell?
+
+#### Write me.
+
+@node Q5.4.2, Q5.4.3, Q5.4.1, External Subsystems
+@unnumberedsubsec Q5.4.2: How do I start up a second shell buffer?
+
+In the @code{*shell*} buffer:
+
+@lisp
+M-x rename-buffer @key{RET} *shell-1* @key{RET}
+M-x shell RET
+@end lisp
+
+This will then start a second shell. The key is that no buffer named
+@samp{*shell*} can exist. It might be preferable to use @kbd{M-x
+rename-uniquely} to rename the @code{*shell*} buffer instead of @kbd{M-x
+rename-buffer}.
+
+Alternately, you can set the variable @code{shell-multiple-shells}.
+If the value of this variable is non-nil, each time shell mode is invoked,
+a new shell is made
+
+@node Q5.4.3, Q5.4.4, Q5.4.2, External Subsystems
+@unnumberedsubsec Q5.4.3: Telnet from shell filters too much
+
+I'm using the Emacs @kbd{M-x shell} function, and I would like to invoke
+and use a telnet session within it. Everything works fine except that
+now all @samp{^M}'s are filtered out by Emacs. Fixes?
+
+Use @kbd{M-x rsh} or @kbd{M-x telnet} to open remote sessions rather
+than doing rsh or telnet within the local shell buffer. You can also
+use @kbd{M-x ssh} to open secure remote session if you have @code{ssh}
+installed.
+
+@node Q5.4.4, Q5.4.5, Q5.4.3, External Subsystems
+@unnumberedsubsec Q5.4.4: Strange things are happening in Shell Mode.
+
+Sometimes (i.e. it's not repeatable, and I can't work out why it
+happens) when I'm typing into shell mode, I hit return and only a
+portion of the command is given to the shell, and a blank prompt is
+returned. If I hit return again, the rest of the previous command is
+given to the shell.
+
+@email{martin@@xemacs.org, Martin Buchholz} writes:
+
+@quotation
+There is a known problem with interaction between @code{csh} and the
+@code{filec} option and XEmacs. You should add the following to your
+@file{.cshrc}:
+
+@example
+if ( "$TERM" == emacs || "$TERM" == unknown ) unset filec
+@end example
+@end quotation
+
+@node Q5.4.5, Q5.4.6, Q5.4.4, External Subsystems
+@unnumberedsubsec Q5.4.5: XEmacs complains "No such file or directory, diff"
+
+or "ispell" or other commands that seem related to whatever you just
+tried to do (M-x ediff or M-$, for example).
+
+There are a large number of common (in the sense that "everyone has
+these, they really do") Unix utilities that are not provided with
+XEmacs. The GNU Project's implementations are available for Windows in
+the the Cygwin distribution (@uref{http://www.cygwin.com/}), which also
+provides a complete Unix emulation environment (and thus makes ports of
+Unix utilities nearly trivial). Another implementation is that from
+MinGW (@uref{http://www.mingw.org/msys.shtml}). If you know of others,
+please let us know!
+
+@node Q5.4.6, Q5.5.1, Q5.4.5, External Subsystems
+@unnumberedsubsec Q5.4.6: Cygwin error "fork_copy: linked dll/bss pass 0 failed"
+
+If you are getting an error like
+
+@example
+17797832 [main] bash 3468 fork_copy: linked dll/bss pass 0 failed,
+0x675000..0x6756A0, done 0, windows pid 2708, Win 32 error 487
+bash: fork: resource temporarily unavailable
+@end example
+
+when trying to run bash using @kbd{M-x shell}, then you need to rebase
+your Cygwin DLL's. This is a known problem with Cygwin. To fix:
+
+@enumerate
+@item
+Download the @file{rebase} utility from Cygwin setup (it's under
+@samp{System}).
+@item
+Kill @strong{all} of your Cygwin processes, including all of your
+shells and all background processes. Use @code{ps -a} to list all the
+processes you need to kill.
+@item
+From a DOS prompt, run @file{ash} (@strong{not} @file{bash},
+@file{tcsh} or @file{zsh}). Do not try to be clever and @code{exec
+/bin/ash} from your last shell; it won't work.
+@item
+Type @code{/bin/rebaseall -v}.
+@end enumerate
+
+The problem should now be fixed -- at least, until you install another
+Cygwin package with DLL's, in which case you may have to repeat the
+procedure.
+
+@unnumberedsec 5.5: Multiple Device Support
+
+@node Q5.5.1, Q5.5.2, Q5.4.6, External Subsystems
+@unnumberedsubsec Q5.5.1: How do I open a frame on another screen of my multi-headed display?
+
+Use the command @kbd{M-x make-frame-on-display}. This command is also
+on the File menu in the menubar.
+
+The command @code{make-frame-on-tty} also exists, which will establish a
+connection to any tty-like device. Opening the TTY devices should be
+left to @code{gnuclient}, though.
+
+@node Q5.5.2, Q5.5.3, Q5.5.1, External Subsystems
+@unnumberedsubsec Q5.5.2: Can I really connect to a running XEmacs after calling up over a modem? How?
+
+Yes. Use @code{gnuclient -nw}.
+
+Also see @ref{Q5.5.3, How do I disable gnuserv from opening a new frame?}.
+
+@node Q5.5.3, Q5.5.4, Q5.5.2, External Subsystems
+@unnumberedsubsec Q5.5.3: How do I disable gnuserv from opening a new frame?
+
+If you set the @code{gnuserv-frame} variable to the frame that should be
+used to display buffers that are pulled up, a new frame will not be
+created. For example, you could put
+
+@lisp
+(setq gnuserv-frame (selected-frame))
+@end lisp
+
+early on in your @file{init.el}, to ensure that the first frame created
+is the one used for your gnuserv buffers.
+
+There is an option to set the gnuserv target to the current frame. See
+@code{Options->Display->"Other Window" Location->Make Current Frame Gnuserv Target}
+
+You can also change this with Customize. Select from the
+@code{Options} menu @code{Advanced
+(Customize)->Emacs->Environment->Gnuserv->Gnuserv Frame...} or type
+@kbd{M-x customize @key{RET} gnuserv @key{RET}}.
+
+
+@node Q5.5.4, Q5.5.5, Q5.5.3, External Subsystems
+@unnumberedsubsec Q5.5.4: How do I start gnuserv so that each subsequent XEmacs is a client?
+
+Put the following in your @file{init.el} file to start the server:
+
+@lisp
+(gnuserv-start)
+@end lisp
+
+Start your first XEmacs as usual. After that, you can do:
+
+@example
+gnuclient randomfilename
+@end example
+
+from the command line to get your existing XEmacs process to open a new
+frame and visit randomfilename in that window. When you're done editing
+randomfilename, hit @kbd{C-x #} to kill the buffer and get rid of the