.\" @(#)workshop.1 1.34 00/02/25 SMI; .TH workshop 1 "00/02/25 Sun WorkShop 6" .ds ]W .SH NAME workshop \- An Integrated Programming Environment .SH SYNOPSIS .B workshop [ .I standard motif toolkit options ] [ .B \-D .I a.out [ .I core | .I pid ] ] [ .B \-s .I editsessionname ] [ .B \-x .I sessionfile-directory ] [ .B \-V ] [ .I projectname ] .SH AVAILABILITY Available on the Solaris(TM) Operating Environment (SPARC Platform Edition) and the Solaris Operating Environment (Intel Platform Edition) versions 2.6, 7, and 8 running CDE or OpenWindows(TM). .SH DESCRIPTION Sun WorkShop(TM) is an integrated programming environment that allows you to build, edit, debug, and browse a program without having to explicitly start individual tools from the command line. .LP You can change your integrated text editor by choosing \f3Options -> Text Editor Options\fP from the Sun WorkShop main window menu bar and selecting an editor in the Text Editor Options dialog box. .LP .SH OPTIONS \f3workshop\fP accepts all standard Motif Toolkit command line options. In addition, the following options are accepted: .TP 5 .BI \-D " a.out [core|pid]" Run WorkShop and start a debugging session. If .I a.out is specified, load this program into the Debugger. If .I core is specified, the Debugger will use it to do post-mortem debugging on .I a.out. If .I pid is specified, the Debugger will attach to the process with the given process id. In this case you can use "-" instead of .I a.out but then the executable information will not be stored in project cache picklists. .TP .BI \-s " editsessionname" Run WorkShop under the edit server named .I editsessionname. If there is no edit server with the given name, WorkShop will start one. If this option is not specified (the default), WorkShop applications will share the same editor. .TP .BI \-x " sessionfile-directory" Read and write Sun WorkShop's session files .I .workshop* in the specified directory rather than the home directory. Allows multiple configurations. .TP .B \-V Display the Sun WorkShop version string on standard output. .TP .I projectname Load the specified project into Sun WorkShop. .LP .SH Starting Sun WorkShop To start Sun WorkShop from a shell, type .B workshop & at the command prompt. .LP .SH Starting Sun WorkShop From Emacs You can start Sun WorkShop directly from the editor without having to return to the command line. When you exit from Emacs, both Sun WorkShop and Emacs close. .LP You can start Sun WorkShop from the XEmacs editor in three ways: .PD 0 .TP 3 .B * Type \f3M-x workshop-start\fP in the minibuffer. .TP .B * Choose .B Start Sun WorkShop from the Tools menu. .TP .B * Click on the WorkShop button in the tool bar. .PD .LP You can start Sun WorkShop from the GNU Emacs editor as follows: .TP 3 .SB 1. Load \f3workshop.el\fP by setting the load path in your \f3.emacs\fP file as follows: .LP .nf (setq load-path (append load-path '("/\f2WorkShop_install_directory\fP/lib"))) (require 'workshop) .fi .LP and then restarting Emacs. .TP 3 .SB 2. Type \f3M-x workshop-start\fP or choose \f3Start Sun WorkShop\fP from the Tools menu. .LP .SH Breaking the Sun WorkShop-Emacs Connection You can break the connection between Emacs and Sun WorkShop with the command \f3M-x workshop-quit\fP, which will end the Sun WorkShop process and continue to run Emacs (if you started Sun WorkShop from Emacs). .LP If you try to start Sun WorkShop from Emacs and Sun WorkShop does not connect to the editor or does not appear at all, choose Quit WorkShop from the WorkShop menu to end the Sun WorkShop process. .LP .SH Customizations .LP .SS Windows .LP Sun WorkShop windows can be customized by changing the default X resource values. The X resource files for Sun WorkShop, named \fBWORKSHOP\fP and \fBESERVE\fP, can be found in the directory: .LP \fIwdir\fP\fB/WS6/lib/locale/\fP\fILANG\fP\fB/app\-defaults/\fP\fICDE\fP .LP where: .PD 0 .TP \fIwdir\fP is the directory where Sun WorkShop was installed, usually \fB/opt/SUNWspro\fP. .TP \fILANG\fP is your current locale, for example, \fBC\fP or \fBja\fP. .TP \fICDE\fP is either \fBCDE\fP or \fBnon-CDE\fP, depending on whether or not Sun WorkShop is running in a CDE environment. .PD .LP You do not have to modify any of the resources in order to use Sun WorkShop. However, if you do want to make modifications, follow these steps: .LP .TP 3 .SB 1. Copy the WorkShop X resource files to be modified to your home directory, or some other private directory on your \f3XUSERFILESEARCHPATH\fP. .TP 3 .SB 2. Modify the resources you are interested in changing. For example, if you wish to change the background color of the push buttons to white, you would set this resource in the WORKSHOP resource file: .IP WORKSHOP*XmPushButton*background: #FFFFFF .TP 3 .LP .SS Function Keys .LP By default, Sun WorkShop binds Emacs function keys to commands useful for interacting with Sun WorkShop. You can disable the key rebinding by re-setting the Emacs variable \f2eserve\-bind\-fkeys\fP. To do this, add the following line to your \f3.emacs\fP file: .LP .nf (setq eserve-bind-fkeys nil) .fi .SH ENVIRONMENT .TP .SB SPRO_LAUNCH_EDITOR_FROM_PATH When launching XEmacs, Sun WorkShop first looks for xemacs in the top-level bin directory of the Sun WorkShop installation. If it cannot find xemacs there, Sun WorkShop searches for it using the \fBPATH\fP environment variable. Setting \fBSPRO_LAUNCH_EDITOR_FROM_PATH\fP to any value disables the check for xemacs in the top-level bin directory of the Sun WorkShop installation. .TP .SB SPRO_LAUNCH_TOOLS_FROM_PATH When launching tools from the main window toolbar or from the Tools menu, Sun WorkShop first looks for a binary in the top-level bin directory of the Sun WorkShop installation. If it cannot find the binary there, Sun WorkShop searches for the binary using the \fBPATH\fP environment variable. Setting \fBSPRO_LAUNCH_TOOLS_FROM_PATH\fP to any value disables the check for the binary in the top-level bin directory of the Sun WorkShop installation. .TP .SB SPRO_DBX_PATH When launching dbx, use this path instead of the default location. .SH SEE ALSO makeprd(1), dbx(1), analyzer(1), codemgr(1), vi(1), vim(1), nedit(1), xemacs(1) .LP The following Sun WorkShop documentation is available online through http://docs.sun.com: .PD 0 .TP 3 .B * .I Introduction to Sun WorkShop .TP .B * .I Analyzing Program Performance With Sun WorkShop .TP .B * .I Debugging a Program With dbx .TP .B * .I Sun WorkShop TeamWare User's Guide .PD .LP